On Tue, 2011-08-30 at 14:01 -0500, Michael Merickel wrote: > The way weberror worked is that it'd dump the URL to the console, and > you could visit that url to see the traceback. I think this was fairly > reasonable.
So I have this working on a branch. It keeps exceptions around and dumps a URL to the console with the token in it that is capable of pulling up an exception page. The remaining obsessing that needs to be done (sort of unrelated, but excavated by the work I did) is that currently there's a boolean setting named "debugtoolbar.intercept_exc". It currently implies that the traceback page both be shown and that the traceback page embeds the debugging controls. However, the underlying machinery allows the pretty traceback to be shown without the debugging controls (only allowing "view source", more or less). I'd like to consider changing the meaning of "debugtoolbar.intercept_exc" to be a tri-state: false: don't catch the exception at all and let it bubble up true: show the traceback without debugging controls debug: show the traceback with debugging controls Any better idea? - C -- 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.
