#31560: Circular imports raise AppRegistryNotReady.
------------------------------+--------------------------------------
Reporter: ExTexan | Owner: nobody
Type: Bug | Status: closed
Component: Core (Other) | Version: 3.0
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Comment (by ExTexan):
In one of my cases, it was a model imported in a signals.py and the
signals.py imported by the same model it imported. Then anything that
tried to import the model would encounter the circular imports. As a
quick test, I just went back to the signals.py file and put the model
import back in. I got ImportError, as you did. There were a slew of
changes I made when I fixed the "Apps aren't loaded yet" issue, so now I
can't be sure what actually caused it in the first place.
I'll need to revert that entire commit and take it one step at a time to
see if I can zero in on the cause. I'll see if I can make time to do
this, but workload is heavy atm, so I can't really say when I'll get to
it.
--
Ticket URL: <https://code.djangoproject.com/ticket/31560#comment:2>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.6c7761eaefcb1dfd79f3949bce523f55%40djangoproject.com.
