#31780: Include the Python traceback in the debug-page footer as a HTML comment
-------------------------------------+-------------------------------------
Reporter: Tom Forbes | Owner: nobody
Type: New feature | Status: closed
Component: Core (Other) | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
technical_500_response | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tom Forbes):
I'd really like you to reconsider closing this. To put it in more general
terms: the #1 use case for the debug page is to locate the error that
caused the exception, and there are plenty of cases where you might have
the raw HTML rather than viewing it in a browser. Right now the debug page
is not helpful at all in this case.
It is indeed in the copy-paste view but that also involves grepping
through *large* volumes of HTML to find it. I don't think it's a problem
to include it in the footer, size doesn't matter for a debug page and the
key metric is "the time it takes you to find the cause of the error". I
cannot see how this does not help reduce that metric.
--
Ticket URL: <https://code.djangoproject.com/ticket/31780#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.a2b48a787dcd57099cd614507c0d24d3%40djangoproject.com.
