On Wed, May 5, 2010 at 3:31 PM, Kevin Howerton <[email protected]> wrote: > I don't think you understand what the code I just posted is doing or > what the issue I described pertains to.
You want Django to globally catch all exceptions and call sys.excepthook. I'm telling you that's a bad idea -- I've tried it, and it breaks a number of sites I have in production. > All I'm asking for is sane defaults, and consistency between > deployment platforms. This isn't important? >From where I stand the defaults are perfectly sane, and deployment is demonstrably consistent -- Django does the same thing regardless of where it's deployed. You're actually asking for the opposite: a special case for mod_wsgi. Can you explain to me why none of the exception hooks already put into Django is sufficient? I've still not been able to glean that from your posts. Jacob -- 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?hl=en.
