[3.7] bpo-33319: Clarify subprocess call docs. (GH-12508)#12509
Merged
miss-islington merged 1 commit intopython:3.7from Mar 23, 2019
Merged
[3.7] bpo-33319: Clarify subprocess call docs. (GH-12508)#12509miss-islington merged 1 commit intopython:3.7from
miss-islington merged 1 commit intopython:3.7from
Conversation
Clarify capturing or suppressing stdout and stderr on the old call APIs. Do not state that they are equivalent to run() calls when they are not implemented using run as that was misleading. Unlike run they cannot handle stdout or stderr being set to PIPE without a risk of deadlock. (cherry picked from commit 7a2e84c) Co-authored-by: Gregory P. Smith <greg@krypto.org>
gpshead
approved these changes
Mar 23, 2019
Contributor
Author
|
@gpshead: Status check is done, and it's a success ✅ . |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clarify capturing or suppressing stdout and stderr on the old call APIs.
Do not state that they are equivalent to run() calls when they are not implemented using run as that was misleading. Unlike run they cannot handle stdout or stderr being set to PIPE without a risk of deadlock.
(cherry picked from commit 7a2e84c)
Co-authored-by: Gregory P. Smith greg@krypto.org
https://bugs.python.org/issue33319