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 berker.peksag
Recipients berker.peksag, eryksun, gdr@garethrees.org, ncoghlan, serhiy.storchaka, vstinner
Date 2017-10-12.14:38:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507819089.6.0.213398074469.issue28647@psf.upfronthosting.co.za>
In-reply-to
Content
> -u doesn't affect stdin buffering, whatever that would mean.

I think we need to document behavior of stdin somewhere, because current the sys.stdin documentation states:

> When interactive, standard streams are line-buffered. Otherwise, they
> are block-buffered like regular text files. You can override this value
> with the -u command-line option.

https://docs.python.org/3/library/sys.html#sys.stdin
History
Date User Action Args
2017-10-12 14:38:09berker.peksagsetrecipients: + berker.peksag, ncoghlan, vstinner, gdr@garethrees.org, serhiy.storchaka, eryksun
2017-10-12 14:38:09berker.peksagsetmessageid: <1507819089.6.0.213398074469.issue28647@psf.upfronthosting.co.za>
2017-10-12 14:38:09berker.peksaglinkissue28647 messages
2017-10-12 14:38:09berker.peksagcreate