[issue10481] subprocess PIPEs are byte streams

A.M. Kuchling added the comment: Thanks for your patch! -- nosy: +akuchling resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue10481] subprocess PIPEs are byte streams

Roundup Robot added the comment: New changeset 267fff541bda by Andrew Kuchling in branch 'default': #10481: describe universal_newlines' effect on communicate()/check_output() output (alternately bytes or strings) http://hg.python.org/cpython/rev/267fff541bda -- nosy: +python-dev _

[issue10481] subprocess PIPEs are byte streams

Changes by A.M. Kuchling : -- versions: +Python 3.5 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10481] subprocess PIPEs are byte streams

Sam Kimbrel added the comment: I've created a patch that updates the docs to reflect the behavior of communicate() and check_output(), which is that both the "input" argument and stdin/stdout/stderr PIPEs will convert to and from strings when self.univeral_newlines is True and must be bytes ot

[issue10481] subprocess PIPEs are byte streams

Glenn Linderman added the comment: Maybe it should also be mentioned that p.stdout and p.stderr and p.stdin, when set to be PIPEs, are also byte streams. Of course that is the reason that communicate accepts and produces byte streams. -- ___ Pytho

[issue10481] subprocess PIPEs are byte streams

New submission from Glenn Linderman : 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 a