#31780: Include the Python traceback in the debug-page footer as a HTML comment
-------------------------------------+-------------------------------------
Reporter: Tom | Owner: nobody
Forbes |
Type: | Status: new
Uncategorized |
Component: | Version: master
Uncategorized | Keywords:
Severity: Normal | technical_500_response
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
It would be very handy to include the traceback that triggered the Django
debug page inside a HTML comment in the footer of the page. Quite often
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.
If we can include just a raw Python traceback in the footer of the debug
page as a HTML comment then this will be immediately discoverable in such
situations. `print(html_response)` and `curl` would both show it without
needing any scrolling or grepping.
--
Ticket URL: <https://code.djangoproject.com/ticket/31780>
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/046.d28ab3a4fb20e081c8343af8f0a47605%40djangoproject.com.
