bernardopires / django-tenant-schemas

Tenant support for Django using PostgreSQL schemas.
https://django-tenant-schemas.readthedocs.org/en/latest/
MIT License
1.45k stars 424 forks source link

After upgrading django 2.0 to 3.0, shell tenant command stop working #641

Open Mario-Cano opened 4 years ago

Mario-Cano commented 4 years ago

I moved from django 2.0 to 3.0 and shell tenant command stop working.

I'm doing something like this

_./manage.py tenantcommand shell --schema=customer1,

I'm getting this error Traceback (most recent call last): File "manage.py", line 15, in execute_from_command_line(sys.argv) File "/home/mario/anaconda3/envs/myapp/lib/python3.6/site-packages/django/core/management/init.py", line 401, in execute_from_command_line utility.execute() File "/home/user/anaconda3/envs/myapp/lib/python3.6/site-packages/django/core/management/init.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/home/user/anaconda3/envs/myapp/lib/python3.6/site-packages/django/core/management/base.py", line 328, in run_from_argv self.execute(*args, cmd_options) File "/home/user/anaconda3/envs/myapp/lib/python3.6/site-packages/django/core/management/base.py", line 369, in execute output = self.handle(*args, *options) File "/home/user/anaconda3/envs/myapp/lib/python3.6/site-packages/tenant_schemas/management/commands/tenant_command.py", line 15, in handle call_command(command, args, options) File "/home/user/anaconda3/envs/myapp/lib/python3.6/site-packages/django/core/management/init.py", line 160, in call_command ', '.join(sorted(valid_options)), TypeError: Unknown option(s) for shell command: skip_checks. Valid options are: command, force_color, help, interface, no_color, no_startup, pythonpath, settings, stderr, stdout, traceback, verbosity, version.

Do you have any suggestion about how to fix it?

estebanangelm commented 4 years ago

I have this exact same issue. It was a very cool feature to start the django console with the single line command. Hope you can fix it!

sshahbaj commented 4 years ago

Check issue #634