pyramid_exclog is placed "under" the exception view tween. This effectively means that the exclog is executed before the HTTPNotFound exception view. I don't have an awesome solution, but wanted to tell you why you're seeing what you're seeing.
On Tue, Jan 10, 2012 at 9:29 AM, Jason <[email protected]> wrote: > I have an exception handling view that handles HTTPNotFound exceptions and > calls a Pylons wsgi application using request.get_response(). If > request.get_response() raises an exception (eg AttributeError) > pyramid_exclog is never called. It is called for the HTTPNotFound exception > (and ignored), but does not get called again when the exception view raises > an exception. > > WebError correctly handled this scenario, but I'm guessing this has > something to do with the difference between a Tween and WSGI Middleware? > > I'm just going to add WebError to the Pylons application's middleware.py, > but any clarification about why the exclog tween doesn't work would be > greatly appreciated. > > --Jason > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/pylons-discuss/-/f8XF-7zbUOkJ. > 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/pylons-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
