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 v+python
Recipients docs@python, v+python
Date 2010-11-21.05:57:01
SpamBayes Score 3.75057e-05
Marked as misclassified No
Message-id <1290319024.08.0.519309863324.issue10481@psf.upfronthosting.co.za>
In-reply-to
Content
While http://bugs.python.org/issue2683 did clarify the fact that the .communicate API takes a byte stream as input, it is easy to miss the implication.  Because Python programs start up with stdin as a text stream, it might be good to point out that some action may need to be taken to be sure that the receiving program expects a byte stream, or that the byte stream supplied should be in an encoding that the receiving program is expecting and can decode appropriately.

No mention is presently made in the documentation for .communicate that its output is also a byte stream, and if text will correspond to whatever encoding is used by the sending program.
History
Date User Action Args
2010-11-21 05:57:04v+pythonsetrecipients: + v+python, docs@python
2010-11-21 05:57:04v+pythonsetmessageid: <1290319024.08.0.519309863324.issue10481@psf.upfronthosting.co.za>
2010-11-21 05:57:01v+pythonlinkissue10481 messages
2010-11-21 05:57:01v+pythoncreate