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 r.david.murray
Recipients aronacher, benjamin.peterson, flox, hynek, martin.panter, pitrou, r.david.murray, stutzbach
Date 2014-05-14.21:54:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1400104467.31.0.515398076175.issue21364@psf.upfronthosting.co.za>
In-reply-to
Content
The issue of (mixed) string and binary input/output on the standard streams is still a bit of a work in progress, I think, both documentation wise and code wise.  So I'm not sure we know yet what the best practice is to recommend here.

I think I agree with Armin, though.  I think mentioning reading binary from sys.stdin.buffer is fine, but suggesting replacing the streams is bad.  If someone figures that out on their own, it's on their own head, but I don't think we should suggest it.

That said, that shutdown error message is probably a bug of one sort or another.
History
Date User Action Args
2014-05-14 21:54:27r.david.murraysetrecipients: + r.david.murray, pitrou, benjamin.peterson, stutzbach, aronacher, flox, hynek, martin.panter
2014-05-14 21:54:27r.david.murraysetmessageid: <1400104467.31.0.515398076175.issue21364@psf.upfronthosting.co.za>
2014-05-14 21:54:27r.david.murraylinkissue21364 messages
2014-05-14 21:54:27r.david.murraycreate