bpo-34886: Fix subprocess.run handling of exclusive arguments#11727
Conversation
gpshead
left a comment
There was a problem hiding this comment.
Please use blurb or blurbit to add the following NEWS entry:
Fix an unintended ValueError from :func:`subprocess.run` when checking for
conflicting `input` and `stdin` or `capture_output` and `stdout` or `stderr` args
when they were explicitly provided but with `None` values within a passed in
`**kwargs` dict rather than as passed directly by name.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
|
Hi @gpshead, thanks for the review! I have made the requested changes; please review again |
|
Thanks for making the requested changes! @gpshead: please review the changes made to this pull request. |
|
Thanks @remilapeyre for the PR, and @gpshead for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8. |
…GH-11727) Fix an unintended ValueError from :func:`subprocess.run` when checking for conflicting `input` and `stdin` or `capture_output` and `stdout` or `stderr` args when they were explicitly provided but with `None` values within a passed in `**kwargs` dict rather than as passed directly by name. (cherry picked from commit 8cc605a) Co-authored-by: Rémi Lapeyre <remi.lapeyre@henki.fr>
|
GH-13916 is a backport of this pull request to the 3.8 branch. |
…GH-11727) Fix an unintended ValueError from :func:`subprocess.run` when checking for conflicting `input` and `stdin` or `capture_output` and `stdout` or `stderr` args when they were explicitly provided but with `None` values within a passed in `**kwargs` dict rather than as passed directly by name. (cherry picked from commit 8cc605a) Co-authored-by: Rémi Lapeyre <remi.lapeyre@henki.fr>
|
GH-13917 is a backport of this pull request to the 3.7 branch. |
|
Thanks @remilapeyre for the PR, and @gpshead for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7. |
Fix an unintended ValueError from :func:`subprocess.run` when checking for conflicting `input` and `stdin` or `capture_output` and `stdout` or `stderr` args when they were explicitly provided but with `None` values within a passed in `**kwargs` dict rather than as passed directly by name. (cherry picked from commit 8cc605a) Co-authored-by: Rémi Lapeyre <remi.lapeyre@henki.fr>
Fix an unintended ValueError from :func:`subprocess.run` when checking for conflicting `input` and `stdin` or `capture_output` and `stdout` or `stderr` args when they were explicitly provided but with `None` values within a passed in `**kwargs` dict rather than as passed directly by name. (cherry picked from commit 8cc605a) Co-authored-by: Rémi Lapeyre <remi.lapeyre@henki.fr>
…GH-11727) Fix an unintended ValueError from :func:`subprocess.run` when checking for conflicting `input` and `stdin` or `capture_output` and `stdout` or `stderr` args when they were explicitly provided but with `None` values within a passed in `**kwargs` dict rather than as passed directly by name.
I think we can skip news for this one.
https://bugs.python.org/issue34886