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 pitrou
Recipients amaury.forgeotdarc, mark, mightyiam, ncoghlan, pitrou, segfaulthunter, srid, vstinner
Date 2011-11-21.17:31:13
SpamBayes Score 5.632834e-09
Marked as misclassified No
Message-id <1321896370.3305.3.camel@localhost.localdomain>
In-reply-to <>
> Firstly, I don't think it makes any sense to set encoding information
> globally for the Popen object. As a simple example, consider using
> Python to write a test suite for the iconv command line tool: there's
> only one Popen instance (for the iconv call), but different encodings
> for stdin and stdout.

Isn't that the exception rather than the rule? I think it actually makes
sense, in at least 99.83% of cases ;-), to have a common encoding
setting for all streams.
(I'm not sure about the "errors" setting, though: should we use strict
for stdin/stdout and backslashreplace for stderr, as the interpreter

Perhaps the common case should be made extra easy.
Date User Action Args
2011-11-21 17:31:13pitrousetrecipients: + pitrou, amaury.forgeotdarc, ncoghlan, vstinner, mark, segfaulthunter, srid, mightyiam
2011-11-21 17:31:13pitroulinkissue6135 messages
2011-11-21 17:31:13pitroucreate