I'll need to see an example. I can't think of anything except an exception view that can replace the response object. Even the toolbar only mutates the body of the response.
On Tue, May 15, 2012 at 9:43 PM, Jonathan Vanasco <jonat...@findmeon.com> wrote: > > > On May 15, 7:33 pm, Michael Merickel <mmeri...@gmail.com> wrote: >> What? Pyramid doesn't have a "debug" code path, minus emitting some >> log messages. Do you mean that the debugtoolbar is doing something to >> the response? > > I'd imagine its either the error screens from pyramid_debugtoolbar or > whatever settings like debug_templates control. > > pyramid.debug_templates = true > pyramid.includes = pyramid_debugtoolbar > > when they're enabled, they seem to hijack the response object and > replease it with their own -- it no longer contains any trace of the > raised exception (unless you regex the debug screen html) > > -- > You received this message because you are subscribed to the Google Groups > "pylons-devel" group. > To post to this group, send email to pylons-devel@googlegroups.com. > To unsubscribe from this group, send email to > pylons-devel+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pylons-devel?hl=en. > -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
