Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
1a13efb7
Commit
1a13efb7
authored
Sep 11, 2019
by
Tim Hoffmann
Committed by
Stéphane Wirtel
Sep 11, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Minor ReST formatting fixes in subprocess docs (#14876)
parent
c78dae8d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
Doc/library/subprocess.rst
Doc/library/subprocess.rst
+4
-4
No files found.
Doc/library/subprocess.rst
View file @
1a13efb7
...
...
@@ -1048,7 +1048,7 @@ calls these functions.
Run the command described by *args*. Wait for command to complete, then
return the :attr:`~Popen.returncode` attribute.
Code needing to capture stdout or stderr should use :func:`run` instead:
Code needing to capture stdout or stderr should use :func:`run` instead:
:
run(...).returncode
...
...
@@ -1076,7 +1076,7 @@ calls these functions.
:exc:`CalledProcessError` object will have the return code in the
:attr:`~CalledProcessError.returncode` attribute.
Code needing to capture stdout or stderr should use :func:`run` instead:
Code needing to capture stdout or stderr should use :func:`run` instead:
:
run(..., check=True)
...
...
@@ -1198,8 +1198,8 @@ becomes::
p1.stdout.close() # Allow p1 to receive a SIGPIPE if p2 exits.
output = p2.communicate()[0]
The
p1.stdout.close() call after starting the p2 is important in order for p1
to receive a SIGPIPE if p2 exits before p1.
The
``p1.stdout.close()`` call after starting the p2 is important in order for
p1
to receive a SIGPIPE if p2 exits before p1.
Alternatively, for trusted input, the shell's own pipeline support may still
be used directly:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment