it helps but not the same thing. e.g.: Right now, I'm having an issue with the auth.register action that doesn't seem to work ( http://www.digitalloft.org/homepage/default/user/register ). I wanted to print markers to get the position in the code that is being executed so I can infer the flow behind this situation. the request.toolbar() doesn't give me that, although it seems very useful.
Any ideas on how to read prints done in WSGI web2py apps? Thank you On Jun 16, 4:55 pm, Massimo Di Pierro <[email protected]> wrote: > does the {{=response.toolbar()}} help? > > On Jun 16, 10:20 am, blackthorne <[email protected]> wrote: > > > > > I'm trying to debug a web2py app working with WSGI on webfaction. > > First, I've activated the Logging = True in the wsgihandler and now I > > can read the httpserver.log. > > I've also read many things on exposing request/response objects but > > what I really wanted would be the possibility to read print calls in > > the app so I can check on variables content throughout the whole > > process. > > > Offline it is easy but how can we do this on a WSGI deployed web2py > > app? > > > Thank you, > > Best regards
