-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-32392: Document env kwarg of subprocess.run method #7289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. When your account is ready, please add a comment in this pull request Thanks again to your contribution and we look forward to looking at it! |
@@ -39,7 +39,7 @@ compatibility with older versions, see the :ref:`call-function-trio` section. | |||
|
|||
.. function:: run(args, *, stdin=None, input=None, stdout=None, stderr=None,\ | |||
shell=False, cwd=None, timeout=None, check=False, \ | |||
encoding=None, errors=None, text=None) | |||
encoding=None, errors=None, text=None, env=None) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a brief description of what env
is? Copying the existing documentation would be enough:
If *env* is not ``None``, it must be a mapping that defines the environment
variables for the new process; these are used instead of the default
behavior of inheriting the current process' environment.
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 |
Thank you for your reveiw. I have made the requested changes; please review again. I've added a sentence referencing |
Thanks for making the requested changes! @berkerpeksag: please review the changes made to this pull request. |
Looks good to me, thank you! I will wait until Monday to give @gpshead time to review this since he's the maintainer of the subprocess module. |
Thanks @rixx for the PR, and @berkerpeksag for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7. |
Thanks! |
…H-7289) (cherry picked from commit af1ec97) Co-authored-by: Tobias Kunze <[email protected]>
GH-7423 is a backport of this pull request to the 3.7 branch. |
Sorry, @rixx and @berkerpeksag, I could not cleanly backport this to |
@rixx would you like to submit a backport PR for 3.6? |
(cherry picked from commit af1ec97) Co-authored-by: Tobias Kunze <[email protected]>
GH-7489 is a backport of this pull request to the 3.6 branch. |
As discussed in bpo-32392, I added the
env
kwarg to the subprocess.run documentation.https://bugs.python.org/issue32392