Pesto doesn't try to do anything related to catching or logging
application errors, so these tracebacks must be being generated upstream
by cherrypy.
Running your test code under wsgiref doesn't show the problem, which
confirms that these tracebacks must be coming from cherrypy. I had a
quick look at the cherrypy docs for error handling but I couldn't
quickly see what you need to configure to turn off these tracebacks.
It's unfortunate that wsgilog doesn't seem to be catching these errors
as it should. I had a look at the wsgilog source code and I think it is
failing to catch exceptions raised while iterating the response. Because
of the way that pesto interfaces with wsgi pretty much all exceptions
will be raised at this stage. It might be worth talking to the author of
wsgilog about this as I'm sure it will affect other wsgi applications too.
Olly.
Thanks for taking the time to look into this even into the cherrypy
docs and wsgilog source. It's much appreciated, since you've saved me
a lot of time knowing now that it's not a pesto issue. I'll
investigate further and will post my findings.
-Sam
> --
> You received this message because you are subscribed to the Google Groups
> "Pesto" group.
> To post to this group, send email to python...@googlegroups.com.
> To unsubscribe from this group, send email to
> python-pesto...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/python-pesto?hl=en.
>
>