[Django] #30464: 'AppRegistryNotReady' error after Django Upgrade from 1.8 to 1.11 version
Django
-------------------------------------+-------------------------------------
Reporter: vinay | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: | Version: 1.11
Uncategorized | Keywords: Django Upgrade,
Severity: Normal | Django-1.11, Django-1.8,
Triage Stage: | AppRegistryNotReady
Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
In our process of upgrading our Django project from 1.8 to 1.11 version,
we removed all the deprecation warnings/errors according to Django-1.11
release notes.
But, after updating the Django version to 1.11 in the project's virtual
environment, we got the following error:
{{{
raise AppRegistryNotReady("Apps aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
}}}
We have many installed apps in the project and using PostgreSQL-9.5
database. We know that the apps which have model classes in it, cause this
error to occur.
The above error even occured when connecting to the database using
connection cursor:
{{{
django.db.connection.cursor().execute()
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30464>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: vinay | Owner: nobody
Cleanup/optimization |
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution: duplicate
Keywords: Django Upgrade, | Triage Stage:
Django-1.11, Django-1.8, | Unreviewed
AppRegistryNotReady |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => duplicate
Comment:
Duplicate of #30452.
Even if you now use Django 1.11, this is still a support question, not a
bug report, unless you can find by debugging that Django is at fault. You
should definitely search for help in support channels. And for that, you
will also need more information, because without access to your code and
at least a full traceback, nobody will be able to help.
--
Ticket URL: <https://code.djangoproject.com/ticket/30464#comment:1>