Malcolm Tredinnick wrote: > > On Fri, 2008-03-07 at 21:03 -0800, Ken Arnold wrote: >> I just hacked together http://www.djangosnippets.org/snippets/631/ >> which includes the technical_500 error view page with the admin error >> email. I did this after seeing a Django site have lots of small errors >> that were difficult to track down because the traceback didn't have >> enough information. Any reason not to include this, as at least an >> option? (or even have some way of overriding the error behavior in a >> subclass, so I don't have to patch the core for this?) > > Personally, I'd prefer to allow overriding what happens in the technical > 500 response path rather than add something like this.
This is already possible, in a way. Django sends "got_request_exception" signal on request exceptions that can be handled by an external function analysing data from sys.exc_info(), unwinding traceback etc. We use it in a production environment logging exceptions on disk instead of sending them by email because it's more convenient to look at and because of fear that a single stupid error could DOS our own email server :-). To tell Django not to send admin emails it's usually enough to leave ADMINS settings empty. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
