Realized today that by default django more or less suppresses errors sent to stderr when debug is off. Well I guess it uses email sent to admins by default. Though, I distinctly remember stderr being sent into my apache logs for some reason. Maybe this was when I was using mod_python rather than mod_wsgi?
I think that comprehensive logging might be beneficial in the long-run. Not sure if django currently has any logging that occurs at various levels? For starters though, we should patch the default behavior so that it logs errors to the python logging system when it handles an exception. I can do this, and even write some documentation on how to setup and use a simple python logger. Where would be the most appropriate place for this patch? Right now I just created a custom server_error view that takes care of it, but perhaps it would be more appropriate for it to be in core/handlers/base.handle_uncaught_exception ? http://code.djangoproject.com/browser/django/trunk/django/core/handlers/base.py#L148 or here? http://code.djangoproject.com/browser/django/trunk/django/views/defaults.py#L16 Thanks guys, -k -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
