Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(160766)

#17987: test.support.captured_stderr, captured_stdin not documented

Can't Edit
Can't Publish+Mail
Start Review
Created:
6 years, 6 months ago by fdrake
Modified:
6 years, 6 months ago
Reviewers:
storchaka
CC:
fdrake_gmail.com, r.david.murray, docs_python.org, devnull_psf.upfronthosting.co.za, storchaka, dmi.baranov
Visibility:
Public.

Patch Set 1 #

Patch Set 2 #

Patch Set 3 #

Patch Set 4 #

Total comments: 2

Patch Set 5 #

Patch Set 6 #

Unified diffs Side-by-side diffs Delta from patch set Stats Patch
Doc/library/test.rst View 1 2 3 4 5 1 chunk +19 lines, -7 lines 0 comments Download
Lib/test/support.py View 1 2 3 4 5 1 chunk +17 lines, -2 lines 0 comments Download
Lib/test/test_support.py View 1 2 3 4 5 1 chunk +10 lines, -7 lines 0 comments Download
Misc/ACKS View 1 2 3 4 5 1 chunk +1 line, -0 lines 0 comments Download

Messages

Total messages: 1
storchaka_gmail.com
6 years, 6 months ago #1
http://bugs.python.org/review/17987/diff/8258/Doc/library/test.rst
File Doc/library/test.rst (right):

http://bugs.python.org/review/17987/diff/8258/Doc/library/test.rst#newcode365
Doc/library/test.rst:365: .. function:: captured_stderr()
I think functions should be mentioned in order of it's fd numbers (0 - stdin, 1
- stdout, 2 - stderr).

http://bugs.python.org/review/17987/diff/8258/Doc/library/test.rst#newcode373
Doc/library/test.rst:373: with captured_stderr() as s:
captured_stdout() is much more used and stdout usually mentioned before stderr.
Sign in to reply to this message.

RSS Feeds Recent Issues | This issue
This is Rietveld 894c83f36cb7+