I think the mailing list might be a better place to start/have this discussion on policy. But I've made a ticket (#18003) so it can be officially dealt with an recorded.
I've had trouble with debugging exceptions passing through or coming from django on several occasions because exceptions were caught then wrapped and re-raised, effectively killing the originating exception's call stack. So I feel strongly that django should have as a matter of policy that originating call stacks should be preserved for raised exceptions in naked or overly broad except blocks. What are the downsides to having this? I think the performance impact will be negligible and acceptable considering this is on an exception path. Let's not unnecessarily throw away information that can be very useful to debugging. Comments/Suggestions/Criticisms? Glenn -- 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.
