#6862: Stack traces from non-DEBUG exceptions can't find source lines when DEBUG
500 pages can.
-------------------------------------+--------------------------------------
Reporter: nedbatchelder | Owner: mtredinnick
Status: new | Milestone:
Component: Core framework | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------------+--------------------------------------
Changes (by mtredinnick):
* owner: nobody => mtredinnick
Comment:
So this looks like a good idea and fits in with some other refactoring we
need to do there. There's one small drawback; this change means that the
debug code handling is ''always'' loaded even when `DEBUG=False`. That's a
slight extra bit of memory usage that Adrian, in particular, likes to
avoid and I don't mind his approach as a general guideline either.
Pulling this stuff out certainly allows somebody to easily subclass the
`django.core.handlers.*` class of their choice and override the
`_get_traceback()` method. I similarly want to pull out some of the other
500 handling so that, e.g, you're not required to have the emailing happen
and that will be done via subclassing as well.
So I'll take care of committing this, but I don't think it will be on by
default. It will be available to request/response handling subclasses,
though, which is a nice way things both ways.
--
Ticket URL: <http://code.djangoproject.com/ticket/6862#comment:3>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
