This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients dmi.baranov, docs@python, fdrake, serhiy.storchaka
Date 2013-05-28.13:42:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369748553.27.0.798893328597.issue17987@psf.upfronthosting.co.za>
In-reply-to
Content
> 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().
History
Date User Action Args
2013-05-28 13:42:33serhiy.storchakasetrecipients: + serhiy.storchaka, fdrake, docs@python, dmi.baranov
2013-05-28 13:42:33serhiy.storchakasetmessageid: <1369748553.27.0.798893328597.issue17987@psf.upfronthosting.co.za>
2013-05-28 13:42:33serhiy.storchakalinkissue17987 messages
2013-05-28 13:42:33serhiy.storchakacreate