What is the actual problem you are trying to solve on GAE? Graham
On Feb 11, 4:20 pm, mdipierro <mdipie...@cs.depaul.edu> 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) > > ['__class__', '__delattr__', '__doc__', '__enter__', '__exit__', > '__getattribute__', '__hash__', '__init__', '__iter__', '__new__', > '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__str__', > 'close', 'closed', 'encoding', 'fileno', 'flush', 'isatty', 'mode', > 'name', 'newlines', 'next', 'read', 'readinto', 'readline', > 'readlines', 'seek', 'softspace', 'tell', 'truncate', 'write', > 'writelines', 'xreadlines'] > > On Feb 10, 10:19 pm, Graham Dumpleton <graham.dumple...@gmail.com> > wrote: > > > > > On Feb 11, 12:58 pm, mdipierro <mdipie...@cs.depaul.edu> 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.info(data) > > > sys.stdout = Logger() > > > Not sufficient as there are lots of methods that a file like object > > should have and which all manner of software for whatever reason like > > to try and use. > > > One could implement a sys.stdout replacement, but that above is way to > > simplistic. > > > Graham -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
