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.12:58:13
SpamBayes Score 5.8517774e-08
Marked as misclassified No
Message-id <>
I agree with Florian Mayer that the encoding handling should be
stream-specific. You could easily be reading the stdout of some third
party program that uses, say, latin1, but want to do your own output in,
say, utf-8.

One solution that builds on what Amaury Forgeot d'Arc has done (i.e.,
the encoding and errors parameters) by allowing those parameters to
accept either a single string (as now), or a dict with keys 'stdin',
'stdout', 'stderr'. Of course it is possible that the client might not
specify all the dict's keys in which case those would use the normal
default (local 8-bit etc.)
Date User Action Args
2009-12-31 12:58:15marksetrecipients: + mark, amaury.forgeotdarc, pitrou, segfaulthunter, srid, mightyiam
2009-12-31 12:58:15marksetmessageid: <>
2009-12-31 12:58:13marklinkissue6135 messages
2009-12-31 12:58:13markcreate