[issue33319] `subprocess.run` documentation doesn't tell is using `stdout=PIPE` safe

Change by Gregory P. Smith : -- nosy: -miss-islington resolution: -> fixed stage: patch review -> commit review status: open -> closed ___ Python tracker ___

[issue33319] `subprocess.run` documentation doesn't tell is using `stdout=PIPE` safe

miss-islington added the comment: New changeset 9cdac5ced68f1d6ef5e1eee7552bb200b46adc23 by Miss Islington (bot) in branch '3.7': bpo-33319: Clarify subprocess call docs. (GH-12508) https://github.com/python/cpython/commit/9cdac5ced68f1d6ef5e1eee7552bb200b46adc23 -- nosy:

[issue33319] `subprocess.run` documentation doesn't tell is using `stdout=PIPE` safe

Change by miss-islington : -- pull_requests: +12460 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33319] `subprocess.run` documentation doesn't tell is using `stdout=PIPE` safe

Gregory P. Smith added the comment: New changeset 7a2e84c3488cfd6c108c6b41ff040825f1757566 by Gregory P. Smith in branch 'master': bpo-33319: Clarify subprocess call docs. (GH-12508) https://github.com/python/cpython/commit/7a2e84c3488cfd6c108c6b41ff040825f1757566 --

[issue33319] `subprocess.run` documentation doesn't tell is using `stdout=PIPE` safe

Change by Gregory P. Smith : -- keywords: +patch pull_requests: +12459 stage: needs patch -> patch review ___ Python tracker ___

[issue33319] `subprocess.run` documentation doesn't tell is using `stdout=PIPE` safe

Martin Panter added the comment: This is a regression in the 3.7+ documentation. It previously said “To [capture output], pass PIPE for the ‘stdout’ and/or ‘stderr’ arguments”. This was removed by Bo Bayles in Issue 32102. -- keywords: +3.7regression nosy: +bbayles, gregory.p.smith,

[issue33319] `subprocess.run` documentation doesn't tell is using `stdout=PIPE` safe

Pekka Klärck added the comment: My goal is to read stdout. It's good to hear `subprocess.run()` is deadlock-safe and I can use it safely. Making the docs explicit about it so that others know it's safe would in my opinion be a good idea as well. Casual users don't

[issue33319] `subprocess.run` documentation doesn't tell is using `stdout=PIPE` safe

Josh Rosenberg added the comment: If the goal is just to suppress stdout, that's what passing subprocess.DEVNULL is for (doesn't exist in Py2, but opening os.devnull and passing that is a slightly higher overhead equivalent). subprocess.run includes a call to

[issue33319] `subprocess.run` documentation doesn't tell is using `stdout=PIPE` safe

Change by Pekka Klärck : -- assignee: -> docs@python components: +Documentation nosy: +docs@python ___ Python tracker ___

[issue33319] `subprocess.run` documentation doesn't tell is using `stdout=PIPE` safe

New submission from Pekka Klärck : I'm porting old scripts from Python 2.7 to 3.6 and plan to change `subprocess.call()` to `subprocess.run()` at the same time. When using `call()` I've used `tempfile.TemporaryFile` as stdout because it's documentation has this