On Tue, 2011-08-30 at 15:34 -0500, Michael Merickel wrote: > The toolbar should be configured to *always* dump out the url to the > traceback in the logger as well as display the url in the web page > rendered for the traceback. > > > I think part of the point of the debugtoolbar is the interactive > traceback so I'd like to see 'debug' remain as the default, or rename > the setting so that 'true' is the interactive and 'readonly' is the > one the user might change it to.
pyramid_debugtoolbar 0.9.1 has been released to PyPI with the show-url-on-console feature and everything else we've been talking about. - C > > On Tue, Aug 30, 2011 at 3:23 PM, Bruce Wade <bruce.w...@gmail.com> > wrote: > I like that idea, then at least there is the option of having > debugging controls for those who want/need them. > > > > On Tue, Aug 30, 2011 at 1:15 PM, Chris McDonough > <chr...@plope.com> wrote: > 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 > pylons-discuss@googlegroups.com. > To unsubscribe from this group, send email to > pylons-discuss+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > > > > > > > -- > -- > Regards, > Bruce Wade > http://ca.linkedin.com/in/brucelwade > http://www.wadecybertech.com > http://www.warplydesigned.com > http://www.fitnessfriendsfinder.com > > > -- > > > You received this message because you are subscribed to the > Google Groups "pylons-discuss" group. > To post to this group, send email to > pylons-discuss@googlegroups.com. > To unsubscribe from this group, send email to pylons-discuss > +unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > > > > > > -- > > Michael > > > -- > You received this message because you are subscribed to the Google > Groups "pylons-discuss" group. > To post to this group, send email to pylons-discuss@googlegroups.com. > To unsubscribe from this group, send email to pylons-discuss > +unsubscr...@googlegroups.com. > 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 pylons-discuss@googlegroups.com. To unsubscribe from this group, send email to pylons-discuss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
