#24829: TemplateView raises unhandled ContentNotRenderedError error when used as
error handler
-------------------------------+------------------------------------
Reporter: nonZero | Owner: nobody
Type: New feature | Status: new
Component: Generic views | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* version: 1.8 => master
* needs_docs: => 0
* type: Bug => New feature
* stage: Unreviewed => Accepted
Comment:
I'm wondering if you have a compelling use case for class-based views as
error handlers? Your example reproduces the default view as far as I can
tell. I'm not sure what changes would be required to support this, but I'd
think it would be nice to keep the error handling code as simple as
possible. That said, if we decide not to fix this we should at least
document the restriction.
--
Ticket URL: <https://code.djangoproject.com/ticket/24829#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.bd35875068966cc5a069d8679d48af27%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
