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.