#25477: Modelbase.__new__ causes `AppRegistryNotReady`
---------------------------------+--------------------------------------
Reporter: cdestigter | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: 1.9a1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by aaugustin):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
"Loading apps" means "importing the Python package containing each app". A
deprecation path was started in Django 1.7 to require that Django can
import apps before importing models so this is indeed no longer supported.
Please review the 1.7 release notes and make sure your code runs without
deprecation warnings on 1.8 before running it on 1.9. The 1.9 release
notes already point to the deprecation timeline where this change is
explained.
--
Ticket URL: <https://code.djangoproject.com/ticket/25477#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.4340b2d50a1a8de84578de082622a86f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
