Rename DEBUG_PROPAGATE_EXCEPTIONS to PROPAGATE_EXCEPTIONS.

[Adam Johnson]

The rarely needed setting DEBUG_PROPAGATE_EXCEPTIONS is confusingly named. It applies all the time, not just when DEBUG = True.

I propose renaming it to PROPAGATE_EXCEPTIONS with the standard deprecation period.

[Mariusz Felisiak]

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.

[Adam 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. Agree the documentation is probably fine though.

[Mariusz Felisiak]

Replying to 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).