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 serhiy.storchaka
Recipients berker.peksag, eryksun,, ncoghlan, serhiy.storchaka, vstinner
Date 2017-10-12.14:17:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
stdin is mentioned in the documentation of the -u option only due to weird internal buffering in Python 2, because user can expect that -u disables it. It is documented what methods use internal buffering and how get rid of it. No other buffering is mentioned.

This no longer actual in Python 3. I think there is no need to mention stdin in the context of the -u option at all. -u doesn't affect stdin buffering, whatever that would mean. Period.

Alternatively you can include a lecture about different kinds of buffering and how -u doesn't affect them.
Date User Action Args
2017-10-12 14:17:18serhiy.storchakasetrecipients: + serhiy.storchaka, ncoghlan, vstinner,, berker.peksag, eryksun
2017-10-12 14:17:18serhiy.storchakasetmessageid: <>
2017-10-12 14:17:18serhiy.storchakalinkissue28647 messages
2017-10-12 14:17:18serhiy.storchakacreate