Author davidsarah
Recipients David.Sankel, amaury.forgeotdarc, brian.curtin, christian.heimes, christoph, davidsarah, ezio.melotti, hippietrail, lemburg, mark, pitrou, santoso.wijaya, sorin, terry.reedy, tim.golden, tzot, v+python, vstinner
Date 2011-03-26.00:18:52
SpamBayes Score 7.69166e-07
Marked as misclassified No
Message-id <1301098732.74.0.914817391114.issue1602@psf.upfronthosting.co.za>
In-reply-to
Content
I wrote:
> A similar issue arises for stdin: to maintain strict compatibility, every read from a TextIOWrapper attached to an input console would have to drain the buffer of its buffer object, in case the app has read from it. This is a bit tricky because the bytes drained from the buffer have to be converted to Unicode, so what happens if they end part-way through a multibyte character? Ugh, I'll have to think about that one.

It seems like there is no correct way for an app to read from both sys.stdin, and sys.stdin.buffer (even without these console changes). It must choose one or the other.
History
Date User Action Args
2011-03-26 00:18:52davidsarahsetrecipients: + davidsarah, lemburg, terry.reedy, tzot, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, tim.golden, mark, christoph, ezio.melotti, v+python, hippietrail, sorin, brian.curtin, santoso.wijaya, David.Sankel
2011-03-26 00:18:52davidsarahsetmessageid: <1301098732.74.0.914817391114.issue1602@psf.upfronthosting.co.za>
2011-03-26 00:18:52davidsarahlinkissue1602 messages
2011-03-26 00:18:52davidsarahcreate