#25477: Modelbase.__new__ causes `AppRegistryNotReady`
------------------------------+------------------------------------
Reporter: cdestigter | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: 1.9a1
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 cdestigter):
Apologies for the delay. I had a little baby girl in the meantime, so had
other things on my mind than this ticket :)
I tried to bisect the deprecation warning change, but I couldn't find any
deprecation warnings with any versions in 1.7.x or 1.8.x. (I did see other
unrelated deprecation warnings, so it's not that I had them turned off or
anything). In addition several django-internal methods have been altered
several times (`Model._meta` refactor) between 1.7 and 1.9 so it was too
confusing to bisect.
I've pushed django-typed-models 0.5.0 which works with django 1.9. Users
will just have to change their import path when upgrading.
--
Ticket URL: <https://code.djangoproject.com/ticket/25477#comment:4>
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.943fe1f9f064ee963bf1df1766ec9a46%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
