#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: needsinfo
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 Runner15):
I have it reproduced in Django 2.2.1, as that is where the error message
posted in the original ticket was from. It does not give the error
location nor does it restart the development server.
Replying to [comment:3 felixxm]:
> It looks like a duplicate of #30323. I'm able to reproduce this in
Django 2.2 but in 2.2.1 everything works as expected. See
[https://docs.djangoproject.com/en/2.2/releases/2.2.1/ release notes]:
>
> > Fixed a regression in Django 2.2 that caused a crash of runserver when
URLConf modules raised exceptions (#30323).
--
Ticket URL: <https://code.djangoproject.com/ticket/30500#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.6f8c4e7d6686229e5dbdbc9f311f269a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
