#31280: Rename DEBUG_PROPAGATE_EXCEPTIONS to PROPAGATE_EXCEPTIONS.
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: nobody
Johnson |
Type: | Status: closed
Cleanup/optimization |
Component: HTTP handling | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by felixxm):
Replying to [comment:3 Adam (Chainz) Johnson]:
> I think there are use cases outside of DEBUG=True, for example in tests
to check what exceptions are raised when using test client/webtest (how I
have used it) or if you want to use WSGI middleware to serve your error
pages.
I totally agree, I meant `... only for debugging ...` (with no implication
to the `DEBUG` setting).
--
Ticket URL: <https://code.djangoproject.com/ticket/31280#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.22ed4441e0e700c28abbba18409f2d5e%40djangoproject.com.
