[issue33339] Using default encoding with `subprocess.run()` is not obvious

Eryk Sun added the comment: This issue was already addressed for 3.x in bpo-31756, which added the a `text` parameter and updated the documentation. As to 2.7, it was officially retired as of the first of this month. Anyway, I don't think there was a pressing need to clarify the

[issue33339] Using default encoding with `subprocess.run()` is not obvious

Change by Xavier Robin : -- nosy: +Xavier Robin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33339] Using default encoding with `subprocess.run()` is not obvious

Change by Terry J. Reedy : -- assignee: -> docs@python components: +Documentation nosy: +docs@python stage: -> needs patch type: -> enhancement versions: +Python 2.7, Python 3.6, Python 3.7, Python 3.8 ___ Python tracker

[issue33339] Using default encoding with `subprocess.run()` is not obvious

New submission from Pekka Klärck : It is possible to use `subprocess.run()` with the system's default encoding by using `universal_newlines=True`. This is very handy, but it's not at all obvious (at least for me) that setting such option has effect on encoding. This is