On Jan 5, 2008 9:27 PM, Brian Harring <[EMAIL PROTECTED]> wrote: > On Tue, Nov 20, 2007 at 02:30:24PM -0600, Gary Wilson Jr. wrote: > > > > We don't seem to be catching exceptions raised in response or request > > middleware, causing bare exceptions to be displayed. Is there a reason > > we are not catching these and displaying pretty error pages? > > > > Which leads me to another observation. There seems to be a bit of > > duplication in the WSGIHandler/ModPythonHandler and > > WSGIRequest/ModPythonRequest classes. > > Resurrecting this email, anyone got a valid reason for not > intercepting these exceptions? > > I know I got a nasty surprise when I noticed it in my apache logs. > > Can't answer as to why it is the way it is, but Gary did open a defect to track the issue, and it has a patch:
http://code.djangoproject.com/ticket/6094 Someone else a couple of weeks ago opened another couple of defects covering the same issue, and when pointed to the first defect updated the patch to apply cleanly against (then-current) trunk. So there's a patch to try and report results of, if you like. No one has piped up to say why this shouldn't be changed, so I'd guess it's just waiting on someone with enough expertise and time to give it some attention. Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
