#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
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: new => closed
* resolution: => wontfix
* component: Uncategorized => Core (Other)
Comment:
Thanks, I understand your intentions, but "raw" traceback is already
included in the ''"Copy-and-past-view"''. IMO we shouldn't add traceback
for the third time in the footer, it can be misleading and will make 500
responses even longer (I saw that you proposed adding it as a HTML
comment).
> ... you might get a debug-page HTML output from tests or other places
where it is inconvenient to try and find the actual cause of the exception
- you have to page up through many kilobytes of HTML content to find the
cause of the exception.
The technical 500 page is not really designed for tests. You can always
use a custom `500.html` for them.
--
Ticket URL: <https://code.djangoproject.com/ticket/31780#comment:3>
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.4c4b767a4445d0625645ddda9923fe72%40djangoproject.com.
