Thanks for your reply. 

I wouldn't know how to catch the exception any further upstream. I add the 
routes (in this case mapping 'front_page' to '/'), call make_wsgi_app, that 
gets run by paste/pserve (I assume), and it invokes my view function 
(front_page) when I point a browser at the site. That is defined as such:

@view_config(route_name='front_page', renderer='front_page.mako')
def front_page(request):
     logged_in_user = request.authenticated_userid

And if that first line throws (because authenticated_userid has never been 
filled in), I never get a traceback.



On Saturday, 13 December 2014 22:48:07 UTC, Bert JW Regeer wrote:
>
> There is not enough information for us to know whether you are catching 
> the exception somewhere, or have it set as the context on a view. 
>
> Bert 
>
> > On Dec 13, 2014, at 15:39 , Ben Sizer <[email protected] <javascript:>> 
> wrote: 
> > 
> > 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 [email protected] <javascript:>. 
> > To post to this group, send email to [email protected] 
> <javascript:>. 
> > Visit this group at http://groups.google.com/group/pylons-discuss. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.

Reply via email to