In wsgihandler if you add: sys.stdout=sys.stderr
does it solve the problem? If so I will add this to trunk. On May 27, 9:04 am, "Joseph.Piron" <[email protected]> wrote: > Hi all, > > a little annoying bug I encountered a minute ago: > > I tried the commit in mercurial versioning for an application running > apache+wgsi_mod, and I got a ticket and this error embedded: > > IOError: sys.stdout access restricted by mod_wsgi: sys.stdout access > restricted by mod_wsgi > > A quick check in the documentation explains: > > IOError: sys.stdout access restricted by mod_wsgi > This is because portable WSGI applications should not write to > sys.stdout or use the 'print' statement without specifying an > alternate file object besides sys.stdout as the target. This > restriction can be disabled for the whole server using the > WSGIRestrictStdout directive, or by mapping sys.stdout to sys.stderr > at global scope within in the WSGI application script file. > > Should not this issue be handled ?
