#30500: Error reporting returns a circular import error on a python formatting
error, and does not restart the development server
-------------------------------------+-------------------------------------
Reporter: Runner15 | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Error reporting | Version: 2.2
Severity: Normal | Resolution: invalid
Keywords: error reporting, | Triage Stage:
error, circular import | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
> I would argue that the ergonomics of Django are harmed...
I totally agree with this sentiment. I'd be happy to reopen if we can pin
down an actionable step. (Bearing in mind Django 3.0 is Python 3.6+ only.)
I'm initially doubtful that a workaround for an obtuse Python bug is going
to be worth our effort... — as you say, who knows?
(I'm pretty sure I used to have to restart the dev server quite frequently
back in the day... — not that that's an argument for anything I suppose.)
--
Ticket URL: <https://code.djangoproject.com/ticket/30500#comment:10>
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/066.efacb8cfc67311571cea9b70f21d8e62%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
