Opened 14 years ago

Closed 14 years ago

#13148 closed (duplicate)


Reported by: Matt Harasymczuk Owned by: nobody
Component: Contrib apps Version: dev
Severity: Keywords: debug
Cc:… Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Recently I was doing a lot of django works and every time I get a django DEBUG screen, there were a lot of unnecessary info, which complicated me a debugging process
in settings there should be an option DEBUG_SHOW_DJANGO_TRACEBACK which depends on value (True, False) shows django correlated traceback

it would be a lot easier than showing a 70 lines of
/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/django/template/ in render_node

than hiding (display hidden) it and displaying only this from my project

and by default display block few lines of code in order to trace error

meta and settings should be displayed hidden (when you need them, then you unhide it)

and this is general problem
error messages are very inaccurate, so much, that sometimes it is hard to find where problem is

maybe adding some debugging output functions
for example when you want to test what is inside a dictionary
d = dict()
d{"asdas": asdasd, "a": "dd"}

and it would display at the debug page its content, and of course types like:
d { - dict
"asdas": object (asdasd),
"a": str("dd")
or similar

I love django and made a lot of projects using it, keep it going folks! I love this framework.

Change History (1)

comment:1 Changed 14 years ago by Russell Keith-Magee

Resolution: duplicate
Status: newclosed

I'm going to close this as a duplicate of #11834 - We don't need an additional setting, we need to improve the visual layout of the debug page. This can mean making internal Django stack frames easier to identify (and therefore ignore), and visually collapsing Django stack frames by default (so you can still get to them, but

Note: See TracTickets for help on using tickets.
Back to Top