The technical 500 page does display a lot of information, but debugging a failure is all about information.
#11834 is helpful (dims django frames) without getting in the way (hiding things). For now, this is a good example of a helpful change with minimal negative impact. I'm sure the 500 page could be better, but I'd need to see a concrete proposal outlining the problems and how the improvements address these problems. Right now this feels like a case of fixing what ain't broken. I On Wednesday, June 8, 2011 at 6:10 PM, Graham King wrote: > This ticket might be a part of what you're looking for: > https://code.djangoproject.com/ticket/11834 > It proposes to dim the django parts of the stacktrace, so the code > which most likely caused the error stands out better, which is > certainly something I'd love to see. > > There's some similar ideas discussed here: > https://groups.google.com/group/django-developers/browse_frm/thread/bd43e2e040a17784/?hl=de&pli=1 > > On 8 June 2011 03:50, Mateusz Harasymczuk <m...@harasymczuk.pl > (mailto: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? > > -- > > Matt Harasymczuk > > http://www.matt.harasymczuk.pl > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Django developers" group. > > To view this discussion on the web visit > > https://groups.google.com/d/msg/django-developers/-/b0pKaV9JR2gzXzRK. > > To post to this group, send email to django-developers@googlegroups.com > > (mailto:django-developers@googlegroups.com). > > To unsubscribe from this group, send email to > > django-developers+unsubscr...@googlegroups.com > > (mailto:django-developers+unsubscr...@googlegroups.com). > > For more options, visit this group at > > http://groups.google.com/group/django-developers?hl=en. > > -- > 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 > (mailto:django-developers@googlegroups.com). > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com > (mailto:django-developers+unsubscr...@googlegroups.com). > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. -- 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.
