That's right - I'm not overriding `sys.argv[2]`.. we probably _should_ come up with a way to override it, though, in case someone wants to use `tenant_command` with `call_command` instead of calling it from the command line..

Although, maybe people shouldn't use `tenant_command` with `call_command` anyways - if they're not running the command from the command line, they can set which schema they're running this on themselves. For example, this is what you should do if you want to use `call_command` somewhere in your code:

    connection.set_tenant(tenant)
    call_command('createsuperuser')

This is what you should NOT do currently in an attempt to achieve the same effect:

    call_command('tenant_command', 'createsuperuser')

The later would NOT work, because `sys.argv[2]` would presumably either not exist, or it would otherwise be something unexpected. For example, if the python process running is `python manage.py runserver 127.0.0.1:8000`, then `tenant_command` will try to run the equivalent of `python manage.py tenant_command 127.0.0.1:8000`

Anyways, the point is you probably should not be using `tenant_command` with `call_command`. Maybe we should mention this in the docs.