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, gdr@garethrees.org, ncoghlan, serhiy.storchaka, vstinner
Date 2017-10-12.11:05:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507806333.95.0.213398074469.issue28647@psf.upfronthosting.co.za>
In-reply-to
Content
In Python 2 there is an internal buffering in xreadlines(), readlines() and file-object iterators. You need to enter many lines first that the program get the first of them. And -u doesn't help.

But in Python 3 the program gets the input right as it becomes available. Reading is not blocked if the input is available. There are internal buffers, but they affect only performance, not the behavior. If you can edit a line before pressing Enter, this is because your terminal buffers a line before sending it to the program. I think it is more correct to say that stdin is always unbuffered in Python 3.
History
Date User Action Args
2017-10-12 11:05:33serhiy.storchakasetrecipients: + serhiy.storchaka, ncoghlan, vstinner, gdr@garethrees.org, berker.peksag, eryksun
2017-10-12 11:05:33serhiy.storchakasetmessageid: <1507806333.95.0.213398074469.issue28647@psf.upfronthosting.co.za>
2017-10-12 11:05:33serhiy.storchakalinkissue28647 messages
2017-10-12 11:05:33serhiy.storchakacreate