Malcolm Tredinnick wrote: > At some point we start to drown in config settings. It's probably better > to just "Do The Right Thing" here (first, decide what the right thing > should be). Having a way to always show the exception (if possible) > seems like the right thing to me. > > The patch in ticket #1852 looks like a good start. I was looking at it > this morning and trying to trace through whether anything else needed > similar modification. Not sure the output it produces is perfect, but it > looks like a good start.
Well ... I'm talking about a different case. Let me explain ... In the very beginning, I often made trivial errors in some functions used by the methods. Sometimes this resulted in exceptions that were ignored and resulted in missing data. This is then hard to spot since you don't get a hint what exception it was. It happens not so often now, but I think it's still an obstacle, especially for beginners. If you don't want to add another settings, how about logging all ignored exceptions in debug mode? Or, why does Django need to ignore exceptions in functions called in templates in the first place? Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
