#25697: Default error views shouldn't silence TemplateDoesNotExist errors if a
custom template name was specified
--------------------------------------+------------------------------------
Reporter: charettes | Owner: yakky
Type: Cleanup/optimization | Status: assigned
Component: Generic views | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by timgraham):
I'm lukewarm on deprecations (since it adds a lot of overhead for us)
instead of making minor backwards incompatible changes in cases like this
where it seems to simply delay revealing probable errors in user code. A
similar case was `select_related()` field name validation where we made a
backwards-incompatible change -- Carl, I believe you said you thought that
should have gone through a deprecation. Just wanted to bring it up for
discussion so I can crystallize my thinking around changes like this.
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/25697#comment:5>
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/067.0adc16970204e79abbc0303a3c5e5e0c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
