#25477: Modelbase.__new__ causes `AppRegistryNotReady`
------------------------------+------------------------------------
Reporter: cdestigter | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by craigds):
Basically something that worked fine in 1.8 (with no deprecation warnings,
AFAICT) no longer works in 1.9, and there wasn't anything in the 1.9
release notes about it. So it was a difficult thing to figure out when
upgrading from 1.8 to 1.9.
You are correct that it was mentioned briefly in the deprecation section
of the 1.7 release notes.
If you don't think it's worth fixing the deprecation warnings for 1.7/1.8,
feel free to close the ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/25477#comment:6>
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/068.5127f3b8cb8928043e05613ea597f76c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
