#31560: Detect circular imports and give appropriate message
-------------------------------------------+------------------------
Reporter: ExTexan | Owner: (none)
Type: Bug | Status: new
Component: Error reporting | Version: 3.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------+------------------------
I just spent an inordinate amount of time debugging an "Apps aren't loaded
yet" issue. Googling wasn't much help as I found posts offering "possible
causes" all over the spectrum. Finally, after repeated searches with
different keywords, I just happened to hit on the right solution.
It turned out to be caused by circular imports. I can't even imagine how
circular imports would cause the "Apps aren't loaded" exception, but
needless to say, that error message doesn't describe the actual situation.
If possible, could circular imports be detected and an appropriate
response given?
--
Ticket URL: <https://code.djangoproject.com/ticket/31560>
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/050.2dbe40abd441618e52f371119844ff44%40djangoproject.com.
