#33723: DEBUG_PROPAGATE_EXCEPTIONS is not honored by runserver
-------------------------------------+-------------------------------------
Reporter: Daniel Hahler | Owner: nobody
Type: New feature | Status: closed
Component: Core (Management | Version: dev
commands) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* needs_better_patch: 0 => 1
* needs_tests: 0 => 1
* needs_docs: 0 => 1
* has_patch: 0 => 1
* resolution: => needsinfo
Comment:
Hey Daniel. Interesting idea. I'm not sure of the benefit… maybe it's
worth it, but I've always found setting a breakpoint in an erroring view
to be sufficient. 🤔
Can I ask you to follow-up on the DevelopersMailingList to see what others
think, and to canvas suggestions on the implementation (as it seems a bit
first pass).
Just as a question: what happens with the `handle_error()` under normal
usage if I have `DEBUG_PROPAGATE_EXCEPTIONS` set? (It seems like a
probable can of worms…) 🤔
--
Ticket URL: <https://code.djangoproject.com/ticket/33723#comment:1>
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/01070180f9e1bfdf-857f4b53-c131-45f4-8fff-6c32f6056609-000000%40eu-central-1.amazonses.com.
