[web2py] Re: wsgi and sys.stdout

2010-02-11 Thread Graham Dumpleton
On Feb 12, 5:54 am, Álvaro Justen [Turicas] wrote: > On Thu, Feb 11, 2010 at 16:29, mdipierro wrote: > > Please, go back to the beginning of the thread. ;-) > > I didn't understand. What if you can't change Apache configuration to > enable stdout? You don't need to change the Apache configurat

[web2py] Re: wsgi and sys.stdout

2010-02-11 Thread mdipierro
you are right. On Feb 11, 12:54 pm, Álvaro Justen [Turicas] wrote: > On Thu, Feb 11, 2010 at 16:29, mdipierro wrote: > > Please, go back to the beginning of the thread. ;-) > > I didn't understand. What if you can't change Apache configuration to > enable stdout? > > > > > On Feb 11, 12:25 pm, Á

Re: [web2py] Re: wsgi and sys.stdout

2010-02-11 Thread Álvaro Justen [Turicas]
On Thu, Feb 11, 2010 at 16:29, mdipierro wrote: > Please, go back to the beginning of the thread. ;-) I didn't understand. What if you can't change Apache configuration to enable stdout? > On Feb 11, 12:25 pm, Álvaro Justen [Turicas] > wrote: >> On Thu, Feb 11, 2010 at 16:10, mdipierro wrote:

[web2py] Re: wsgi and sys.stdout

2010-02-11 Thread mdipierro
Please, go back to the beginning of the thread. ;-) On Feb 11, 12:25 pm, Álvaro Justen [Turicas] wrote: > On Thu, Feb 11, 2010 at 16:10, mdipierro wrote: > > When you call print it sends it to stdout and that is redirect into > > the text of the response so it break pages. > > Using print runnin

Re: [web2py] Re: wsgi and sys.stdout

2010-02-11 Thread Álvaro Justen [Turicas]
On Thu, Feb 11, 2010 at 16:10, mdipierro wrote: > When you call print it sends it to stdout and that is redirect into > the text of the response so it break pages. Using print running web2py on Apache cause exceptions since mod_wsgi does not implement sys.stdout. So I think we need to focus this

[web2py] Re: wsgi and sys.stdout

2010-02-11 Thread mdipierro
When you call print it sends it to stdout and that is redirect into the text of the response so it break pages. On Feb 11, 12:01 am, Graham Dumpleton wrote: > What is the actual problem you are trying to solve on GAE? > > Graham > > On Feb 11, 4:20 pm, mdipierro wrote: > > > I agree. I was propo

[web2py] Re: wsgi and sys.stdout

2010-02-10 Thread Graham Dumpleton
What is the actual problem you are trying to solve on GAE? Graham On Feb 11, 4:20 pm, mdipierro wrote: > I agree. I was proposing an idea more than an implementation. The > methods are not that many anyway and most of them do nothing (like > read()) > > >>> import sys > >>> dir(sys.stdout) > > [

[web2py] Re: wsgi and sys.stdout

2010-02-10 Thread mdipierro
I agree. I was proposing an idea more than an implementation. The methods are not that many anyway and most of them do nothing (like read()) >>> import sys >>> dir(sys.stdout) ['__class__', '__delattr__', '__doc__', '__enter__', '__exit__', '__getattribute__', '__hash__', '__init__', '__iter__', '

[web2py] Re: wsgi and sys.stdout

2010-02-10 Thread Graham Dumpleton
On Feb 11, 12:58 pm, mdipierro wrote: > One of my collaborators pointed me to this. > > http://blog.dscpl.com.au/2009/04/wsgi-and-printing-to-standard-output... > > What about this solution that would also address the issue on GAE? > > class Logger: >     def write(self,data): >          logging