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 vstinner
Recipients amaury.forgeotdarc, mark, mightyiam, pitrou, segfaulthunter, srid, vstinner
Date 2010-12-01.23:14:03
SpamBayes Score 3.598788e-13
Marked as misclassified No
Message-id <>
About the topic:
> subprocess seems to use local 8-bit encoding and gives no choice
I don't understand that: by default, Python 2 and Python 3 use byte strings, so there is no encoding (nor error handler).

I don't see how you can get unicode from a process only using subprocess. But with Python 3, you can get unicode if you set universal_newlines option to True.

So for Python 2, it's a new feature (get unicode), and for Python 3, it's a new option to specify the encoding. The title should be changed to something like "subprocess: add an option to specify stdin, stdout and/or stderr encoding and errors" and the type should be changed to "feature request".

Or am I completly wrong?
Date User Action Args
2010-12-01 23:14:05vstinnersetrecipients: + vstinner, amaury.forgeotdarc, pitrou, mark, segfaulthunter, srid, mightyiam
2010-12-01 23:14:05vstinnersetmessageid: <>
2010-12-01 23:14:03vstinnerlinkissue6135 messages
2010-12-01 23:14:03vstinnercreate