I have been using simple print statements to help with my debugging
and over the weekend they came back to haunt me when I tried to deploy
the beta app using Apache and mod_wsgi. I loaded my app, which works
fine using Paster, and Apache displayed a HTTP 500 error. A quick
check of the Apache error log revealed:

IOError: sys.stdout access restricted by mod_wsgi

I asked the gurus at the mod_wsgi group and they pointed out that
printing to stdout is bad form. Apparently it could confuse some
servers that use CGI or something.

So now, I'm working through my code pulling out the print statements.
Not a huge deal, but a hassle. Paster did not complain at all so I
just assumed that it would discard the print output when I loaded it
on Apache. Not so.

K

References:

http://groups.google.com/group/modwsgi/browse_thread/thread/fe856df100dd88de?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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to