Looks like I can still get tracebacks if I fix the issues that cause the session to throw (DB inaccessible), but why not otherwise?
On Saturday, 13 December 2014 21:40:24 UTC, Ben Sizer wrote: > > I upgraded Pyramid from 1.5.1 to 1.5.2, and upgraded a few other packages > too. Now I no longer get tracebacks when there is an error, just a 500 > screen and a debug toolbar that does not allow me to view the traceback. > > I'd run Pyramid under the debugger to find out what is going wrong, but > that doesn't seem possible since it uses pserve.exe instead of a Python > script to run. > > Judging by the logging, something is breaking early on before the request > is created. I suspect the session system, but I allow exceptions to fall > out of there and Pyramid isn't showing that exception to me in any form. > The logs I do see indicate that the following happens when I request the > front page of my app: it attempts to get a session, then calls the view > function, then attempts to get a session again (perhaps because I try to > access request.authenticated_userid, which probably doesn't exist yet), > then exits the view function (via an exception). > > What do I have to do to see these exceptions? Either in the console, or > the traceback in the Debug toolbar? > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
