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 chris.jerdonek
Recipients Arfrever, amaury.forgeotdarc, chris.jerdonek, eric.araujo, mark, mightyiam, ncoghlan, pitrou, r.david.murray, segfaulthunter, srid, vstinner
Date 2012-08-14.11:12:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> > 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.

FWIW, I recently encountered a scenario (albeit in a test situation) where the ability to set different encodings for stdout and stderr would have been useful to me.  It was while creating a test case for issue 15595.  I was changing the locale encoding for stdout, but I also wanted to leave it unchanged for stderr because there didn't seem to be a way to control the encoding that the child used for stderr.
Date User Action Args
2012-08-14 11:12:06chris.jerdoneksetrecipients: + chris.jerdonek, amaury.forgeotdarc, ncoghlan, pitrou, vstinner, mark, eric.araujo, segfaulthunter, Arfrever, r.david.murray, srid, mightyiam
2012-08-14 11:12:05chris.jerdoneksetmessageid: <>
2012-08-14 11:12:04chris.jerdoneklinkissue6135 messages
2012-08-14 11:12:04chris.jerdonekcreate