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 Arfrever, amaury.forgeotdarc, berwin22, chris.jerdonek, eric.araujo, mark, martin.panter, mightyiam, ncoghlan, pitrou, r.david.murray, segfaulthunter, srid, steve.dower, vstinner
Date 2016-09-06.04:47:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwbzkZO0W+wc2bPQ8H9V7-tOjbP+gV8XMdro2=0M=UYYNA@mail.gmail.com>
In-reply-to <1473134997.4.0.378663760898.issue6135@psf.upfronthosting.co.za>
Content
Nick Coghlan added the comment:
> a. How do folks feel about providing a new "text" parameter to replace the cryptic "universal_newlines=True" that would explicitly be equivalent to "universal newlines with sys.getdefaultencoding()"?

If it's just text=True, I don't see the point of having two options
with the same purpose.

> b. Given (a), what if the new "text" parameter also accepted a new "subprocess.TextConfig" object in addition to the base behaviour of doing a plain bool(text) check to activate the defaults?

Can you give an example? I don't see how the API would be used.
History
Date User Action Args
2016-09-06 04:47:40vstinnersetrecipients: + vstinner, amaury.forgeotdarc, ncoghlan, pitrou, mark, eric.araujo, segfaulthunter, Arfrever, r.david.murray, srid, mightyiam, chris.jerdonek, martin.panter, steve.dower, berwin22
2016-09-06 04:47:40vstinnerlinkissue6135 messages
2016-09-06 04:47:40vstinnercreate