On Wed, Jun 8, 2011 at 11:50 AM, Mateusz Harasymczuk <m...@harasymczuk.pl> wrote: > Hi, > I have been thinking about this for quite a long time. > Can you make an error display page less verbose? > I mean not to exclude those useful information, but to initially fold (hide) > them. > Fold those items: > - Python path at the top yellow background. > - (Hide or fold) django traceback entries > When I have a problem I have to scroll down (passing django calls) few pages > until I am able to find which MY action caused an error. > I know looking at django callback may be useful, but in my case, hardly > ever, and probably for newcommers also. > I am imagining this like that: > At the top of the error page, there are tabs. > Summary, Traceback, Request, Settings, and copy-paste view (feedback view). > Summary tab, contains this yellow background information with PYTHON_PATH > initially folded, and traceback filtered out to include only information > from project not calls from django itself. > Traceback, request and settings tabs as it is right now, but separated for > easy of view. > copy-paste (feedback) - a standardize view for easy of copy-and-paste to the > Internet message boards, groups and so on... > It would need a template refactor and some more js involved, should not be a > hard thing to do. > I read that there is a plan to redesign an error page, but since then, those > modifications should do the job. > What do you think?
I disagree entirely. The stack trace is the first thing I look at, and whilst we need to make it easy for people to learn django, we shouldn't be hiding essential information from people - even if it is just hidden in a separate 'tab'. I also strongly disagree about manipulating the traceback at all. Why would I not want to see where it went wrong inside Django? I also don't buy the 'too much information' argument, I have never been in a situation where a crash report has too much information - most of the time it doesn't have enough. Besides which, if the django error page is not what you desire, you can always write your own middleware to produce your own error page. If you really want to change how django's default error page looks like, producing your own version first would be more compelling (and less bikesheddy). Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
