#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 Keryn Knight):

 Yeah, if I had any real idea about how to move it forwards, I fully
 appreciate that would help :)

 My main concern is twofold:
 - New users are ''potentially'' (though not necessarily) more likely to
 experience a problem if it is a version specific issue, as they may not
 have the skills or opportunity to be on the latest and greatest Python
 version; or if they do encounter it (regardless of version) it is masking
 an actual error.
 - that 2.2 is an LTS, and 3.5 is still one of the supported versions for
 that, so even if there's a ''perceived'' ergonomics regression in
 something as vital as autoreloading (being that wsgi is long-lived but not
 statically typed), the opportunity to ''fix'' it before it's essentially
 is frozen is ''arguably'' perhaps up to December, after which it'd almost
 certainly be a sub-par experience for those sticking with it (and the
 fewer users therein who encounter the problem) for the remainder of it's
 lifetime (until the next LTS in 2022)

 Once upon a time, at least SyntaxError caused a restart to be required
 IIRC, but I think that's not been the case for a while now (I'd check
 further, but I can't recall when it might've been). I can't recall if
 NameError or UnboundLocalError previously caused similar manual restarts,
 but I wouldn't be entirely surprised.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/30500#comment:11>
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.06195e64b059b063c49c630f77f5dc71%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to