Message190209
> I'd rather see captured_stdin handled separately, perhaps with some
> additional comments in the example, to emphasize the intended usage
> pattern:
However all three functions share a description.
sys.stdin also has totally different usage pattern than sys.stdout/stderr, but it's documentation joined with documentation of all sys.std* streams.
I think functions should be mentioned in order of it's fd numbers (0 - stdin, 1
- stdout, 2 - stderr). And example for capture_stdout() looks more appropriate then for capture_stderr(). |
|
Date |
User |
Action |
Args |
2013-05-28 13:42:33 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, fdrake, docs@python, dmi.baranov |
2013-05-28 13:42:33 | serhiy.storchaka | set | messageid: <1369748553.27.0.798893328597.issue17987@psf.upfronthosting.co.za> |
2013-05-28 13:42:33 | serhiy.storchaka | link | issue17987 messages |
2013-05-28 13:42:33 | serhiy.storchaka | create | |
|