Opened 4 years ago

Closed 4 years ago

#32441 closed Uncategorized (needsinfo)

Django 2.0 to 2.2 and python 3.4 to 3.6

Reported by: sanjaygunda12 Owned by: nobody
Component: Uncategorized Version: 2.2
Severity: Release blocker Keywords: Django 2.0 to 2.2
Cc: sanjaygunda12 Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Tim Graham)

I have updated django to 2.0 to 2.2 getting error when i fired python3 manage.py runserver

 python3 manage.py runserver
Performing system checks...

System check identified no issues (0 silenced).
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib64/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/usr/lib64/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "/opt/saas/venv/lib/python3.6/site-packages/django/utils/autoreload.py", line 54, in wrapper
    fn(*args, **kwargs)
  File "/opt/saas/venv/lib/python3.6/site-packages/django/core/management/commands/runserver.py", line 120, in inner_run
    self.check_migrations()
  File "/opt/saas/venv/lib/python3.6/site-packages/django/core/management/base.py", line 453, in check_migrations
    executor = MigrationExecutor(connections[DEFAULT_DB_ALIAS])
  File "/opt/saas/venv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 18, in __init__
    self.loader = MigrationLoader(self.connection)
  File "/opt/saas/venv/lib/python3.6/site-packages/django/db/migrations/loader.py", line 49, in __init__
    self.build_graph()
  File "/opt/saas/venv/lib/python3.6/site-packages/django/db/migrations/loader.py", line 206, in build_graph
    self.load_disk()
  File "/opt/saas/venv/lib/python3.6/site-packages/django/db/migrations/loader.py", line 123, in load_disk
    app_config.label,
TypeError: object() takes no parameters

Change History (2)

comment:1 by sanjaygunda12, 4 years ago

Cc: sanjaygunda12 added

comment:2 by Tim Graham, 4 years ago

Description: modified (diff)
Resolution: needsinfo
Status: newclosed

You need to debug the issue and explain why Django is at fault. See TicketClosingReasons/UseSupportChannels for ways to get help. Please reopen with enough details to reproduce the issue if you find Django at fault.

Note: See TracTickets for help on using tickets.
Back to Top