On Thu, 2009-04-30 at 04:58 -0700, Brian Morton wrote: > I am considering filing an enhancement request but I want to check > first to make sure this functionality doesn't already exist. > > Is there some way to make Django include the contents of session in > the traceback email received from a 500 error?
It's not possible to guarantee that that information will be available or that trying to get that information won't cause further errors. A 500 error is because of an entirely unexpected problem and could potentially be caused by anything, so Django should do the absolute minimum to get out of there at that point -- talking to the database for session data (which is still the common case for storing sessions) is not the minimum. However, if you want to write your handling for those unexpected errors, you can subclass the django.core.handlers.* class that you're using and override the handle_unexpected_exception() method to do whatever you would like. That's why that method is separated out. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
