Message info
 
To: From:Django Subject:Re: [Django] #17828: Admin should not handle IncorrectLookupParameters if settings.DEBUG is set Date:Thu, 29 Mar 2012 06:42:53 -0000
 

#17828: Admin should not handle IncorrectLookupParameters if settings.DEBUG is set
-------------------------------------+-------------------------------------
Reporter: Glenn Washburn | Owner: acdha
<development@> | Status: closed
Type: | Version:
Cleanup/optimization | 1.4-beta-1
Component: contrib.admin | Resolution: fixed
Severity: Release blocker | Triage Stage: Ready for
Keywords: | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Glenn Washburn <devlopment@>):

So, why was my first comment apparently not taken into consideration? Now
that I think about it, every naked except which raises a new exception
'should' as a matter of policy include the stack trace from the previous
exception. Are there any reasons why this should not be done? Just the
exception object without the previous stack turns debugging into a spin of
the roulette wheel. I prefer to have a reasonable chance of debugging
exceptions.

--
Ticket URL: <https://code.djangoproject.com/ticket/17828#comment:11>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to django-updates+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.