On Thu, 20 Jan 2011 22:16:36 -0500
James Y Knight <f...@fuhm.net> wrote:
>
> On Jan 20, 2011, at 9:31 PM, Ezio Melotti wrote:
> >> Modified: peps/trunk/pep-3333.txt
> >> ==============================================================================
> >> --- peps/trunk/pep-3333.txt (original)
> >> +++ peps/trunk/pep-3333.txt Fri Jan 7 16:39:27 2011
> >> @@ -310,9 +310,9 @@
> >> elif not headers_sent:
> >> # Before the first output, send the stored headers
> >> status, response_headers = headers_sent[:] = headers_set
> >> - sys.stdout.write('Status: %s\r\n' % status)
> >> + sys.stdout.buffer.write('Status: %s\r\n' % status)
> >> for header in response_headers:
> >> - sys.stdout.write('%s: %s\r\n' % header)
> >> + sys.stdout.buffer.write('%s: %s\r\n' % header)
> >
> > Also note that .buffer might not be available in some cases (i.e. when
> > sys.stdout has been replaced with other objects).
>
> Do you have a recommendation for a better way to do bytes I/O on
> stdin/sydout, then?...just saying that .buffer might not be available isn't a
> very useful comment unless there's a replacement idiom...
Well, this is the recommmendation. There's no reason for
sys.stdXXX.buffer not to exist if you have full control over the
application (which you normally have if you do CGI).
Regards
Antoine.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
