Re: [Python-Dev] [Python-checkins] r87815 - peps/trunk/pep-3333.txt
On Fri, Jan 7, 2011 at 4:39 PM, phillip.eby python-checkins@python.orgwrote:
Author: phillip.eby Date: Fri Jan 7 16:39:27 2011 New Revision: 87815
Log: More bytes I/O fixes
Modified: peps/trunk/pep-3333.txt
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).
sys.stdout.write('\r\n') sys.stdout.buffer.write(data)
Python-checkins mailing list Python-checkins@python.org http://mail.python.org/mailman/listinfo/python-checkins
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...
James
On Thu, 20 Jan 2011 22:16:36 -0500 James Y Knight foom@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.
participants (3)
-
Antoine Pitrou -
Ezio Melotti -
James Y Knight