#30500: Error reporting returns a circular import error on a python formatting
error, and does not restart the development server
-------------------------------------+-------------------------------------
Reporter: Runner15 | Owner: Tom
Type: | Forbes
Cleanup/optimization | Status: assigned
Component: Error reporting | Version: master
Severity: Normal | Resolution:
Keywords: error reporting, | Triage Stage: Accepted
error, circular import |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
First of all, I'd like to thank you so much for the amazing research
you've done on that issue!
Now saying it's not adding overhead is not completely true, however it's a
minimal overhead (creating lock, entering context manager, ...). And what
about the other occurrences of `import_module` in Django code? I think
that at some point we have to trust Python for not regressing in that
function. So I still think this should be fixed in Django 2.2 but not in
master.
--
Ticket URL: <https://code.djangoproject.com/ticket/30500#comment:18>
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/066.a84505c131f4361dbbfd12e2bf02a068%40djangoproject.com.
