There's some similar ideas discussed here:
https://groups.google.com/group/django-developers/browse_frm/thread/bd43e2e040a17784/?hl=de&pli=1
> --
> 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-d...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-develop...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
I think, adding a link at top, getting you to the end of traceback
would be suitable and would work 96% of times.
e.g, top line with exception type and URL could be a link moving you
to the end of traceback, where the exception happened.
What do you think?
Smart (colored) traceback could change that to moving to the last
piece of code which is not django code, but to be really usable, one
would have to customize it (i.e, to add info what 3rd-party packages
you use), which I feel is wrong.
Tabs would also have this problem, and also that without django lines
traceback would be much less readable.
> --
> 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/-/d0F2R2NvWkJNQ3NK.
> To post to this group, send email to django-d...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-develop...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
--
Best regards, Yuri V. Baburov, Skype: yuri.baburov, MSN: bu...@live.com
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
#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
>
> > To post to this group, send email to django-d...@googlegroups.com (mailto:django-d...@googlegroups.com).
> > To unsubscribe from this group, send email to
> > django-develop...@googlegroups.com (mailto:django-develop...@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-d...@googlegroups.com (mailto:django-d...@googlegroups.com).
> To unsubscribe from this group, send email to django-develop...@googlegroups.com (mailto:django-develop...@googlegroups.com).
On Friday, 10 June 2011 at 04:31, Valentin Golev wrote:
What I'd really like is a stacktrace in a plain text in the html
commentary ("<!-- ... -->") on the very top of the page.
I've opened https://code.djangoproject.com/ticket/16227 with patch
attached.
Regards,
Dan