#30464: 'AppRegistryNotReady' error after Django Upgrade from 1.8 to 1.11
version
-------------------------------------+-------------------------------------
Reporter: vinay | Owner: nobody
Type: | Status: closed
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
-------------------------------------+-------------------------------------
Changes (by Claude Paroz):
* 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>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.70fe5a9b6bd53295e2f698ec54e70baa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
