#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 edmorley):

 This caused confusion for me too - particularly since googling the
 exception (but not specifically django 1.9) brings up a number of
 misleading fixes for older problems.

 It would be great if:
 * The deprecation warning could be fixed in Django 1.8, particularly since
 it's an LTS release.
 * The Django 1.9 release notes could emphasise this breakage a bit more
 than they do currently, perhaps by changing this paragraph:
 > All models need to be defined inside an installed application or declare
 an explicit app_label. Furthermore, it isn’t possible to import them
 before their application is loaded. In particular, it isn’t possible to
 import models inside the root package of an application.
 (https://docs.djangoproject.com/en/1.9/releases/1.9/#features-removed-
 in-1-9)
 ...to mention the `AppRegistryNotReady: Apps aren't loaded yet.` exception
 explicitly.
 * The `AppRegistryNotReady` exception could state what app was being
 loaded, since it's not always clear from the traceback. (And in my case it
 was one of my third party packages that was causing the problem.)

 Many thanks :-)

--
Ticket URL: <https://code.djangoproject.com/ticket/25477#comment:8>
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.383d0b117b281d1da8071bea5b05bf03%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to