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 akira
Recipients akira, serhiy.storchaka
Date 2014-10-23.11:26:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414063581.74.0.138772319327.issue22709@psf.upfronthosting.co.za>
In-reply-to
Content
It is incorrect that sys.stdin is *always* a text stream. It often is,
but not always.

There are cases when it is not e.g., 

   $ tar zcf - stuff | gpg -e | ssh user@server 'cat - > stuff.tar.gz.gpg'

tar's stdout is *not* a text stream.
gpg's stdin/stdout are *not* text streams.
ssh's stdin is *not* a text stream.
etc.

If any of the steps are implemented in Python then it is useful to
consider sys.stdin as a binary stream.

Any script written before Python 3.4.1 (#21075) that used FileInput binary mode
*had to* use sys.stdin = sys.stdin.detach()

A bugfix release should not break working code.
History
Date User Action Args
2014-10-23 11:26:21akirasetrecipients: + akira, serhiy.storchaka
2014-10-23 11:26:21akirasetmessageid: <1414063581.74.0.138772319327.issue22709@psf.upfronthosting.co.za>
2014-10-23 11:26:21akiralinkissue22709 messages
2014-10-23 11:26:21akiracreate