#31280: Rename DEBUG_PROPAGATE_EXCEPTIONS to PROPAGATE_EXCEPTIONS.
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: nobody
Johnson |
Type: | Status: new
Cleanup/optimization |
Component: HTTP handling | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* cc: Luke Plant (added)
Comment:
As far as I'm concerned a `DEBUG_` prefix is to emphasize that this should
be used only for debug and not on live sites. It's also documented
properly:
> If set to `True`, Django's exception handling of view functions
(handler500, or the debug view if `DEBUG` is `True`) and logging of 500
responses (django-request-logger) is skipped and exceptions propagate
upwards.
It's not misleading, IMO. I would keep the current name.
--
Ticket URL: <https://code.djangoproject.com/ticket/31280#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/068.b30f52836ee44db7c0e7f88468b84ec3%40djangoproject.com.
