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 mark
Recipients amaury.forgeotdarc, mark, mightyiam, pitrou, segfaulthunter, srid
Date 2009-12-31.13:43:17
SpamBayes Score 6.6378055e-07
Marked as misclassified No
Message-id <326c4f990912310543y3695747do7438786036010944@mail.gmail.com>
In-reply-to <1262266248.37.0.761556762982.issue6135@psf.upfronthosting.co.za>
Content
On Thu, Dec 31, 2009 at 1:30 PM, Amaury Forgeot d'Arc
<report@bugs.python.org> wrote:
>
> Amaury Forgeot d'Arc <amauryfa@gmail.com> added the comment:
>
> I don't understand. How is the subprocess stdout related to the main
> program output?
> Stream-specific encoding could be useful for subprocesses that expect
> latin-1 from stdin but write utf-8 to stdout. I'm not sure we should
> support this.

Yes, you're right.

(What I had in mind was a scenario where you read one process's stdout
and wrote to another process's stdin; but of course using your errors
& encoding arguments this will work because there'll be two separate
process objects each of which can have its encoding and errors set
separately.)
History
Date User Action Args
2009-12-31 13:43:20marksetrecipients: + mark, amaury.forgeotdarc, pitrou, segfaulthunter, srid, mightyiam
2009-12-31 13:43:18marklinkissue6135 messages
2009-12-31 13:43:17markcreate