This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients M..Z., amaury.forgeotdarc, flox, georg.brandl, ishimoto, loewis, pitrou, python-dev, vstinner
Date 2012-08-05.11:21:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344165522.3488.5.camel@localhost.localdomain>
In-reply-to <>
> Man page of Python says 
>   -u Force  stdin,  stdout  and  stderr to be totally unbuffered.  On
>      systems where it matters, also put stdin, stdout and  stderr  in
>      binary  mode.   

I don't know which version it is, but current 3.3 says:

“Force the binary I/O layers of stdin, stdout and  stderr  to  be
unbuffered.  The text I/O layer will still be line-buffered.”

> test_httpservers depends on this behavior, but was implemented as
> documented in Python 3.

I would argue that test_httpservers is wrong, since it uses print() in a
CGI script where sys.stdout.buffer.write() should really be used.
Date User Action Args
2012-08-05 11:21:18pitrousetrecipients: + pitrou, loewis, georg.brandl, ishimoto, amaury.forgeotdarc, vstinner, flox, M..Z., python-dev
2012-08-05 11:21:18pitroulinkissue13119 messages
2012-08-05 11:21:18pitroucreate