#30752: Allow using ExceptionReporter subclass in
django.views.debug.technical_500_response
---------------------------------+---------------------------------------
Reporter: Carlton Gibson | Owner: Pavel Lysak
Type: New feature | Status: assigned
Component: Error reporting | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
---------------------------------+---------------------------------------
Comment (by Pavel Lysak):
Hi!
But as i see handler500 and technical_500_response are different things.
The first is view which we can set in settings and which runs when DEBUG =
False.
The second one runs when DEBUG = True. And it called from
response_for_exception and handle_uncaught_exception. So i don't think
that we can use functools.partial when providing the handler500 in the
URLConf.
Am i wrong?
--
Ticket URL: <https://code.djangoproject.com/ticket/30752#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.34b28894f37b32f885f0af8cbd2d24de%40djangoproject.com.
