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 xx11mz
Recipients docs@python, xx11mz
Date 2022-01-10.05:59:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1641794388.21.0.0521440708614.issue46325@roundup.psfhosted.org>
In-reply-to
Content
SubprocessTransport.get_pipe_transport returns a "transport for the communication pipe corresponding to the integer file descriptor fd".
Below that, it currently says fd 0 is readable and fd 1 and 2 are writable.

But since it is referring to the subprocess' file descriptors from the perspective of the parent process, I believe fd 0 should be writable while fd 1 and 2 are readable. In other words, the parent process can write to the subprocess' stdin and read from its stdout and stderr.

Maybe I have completely misunderstood this method, but I have confirmed that get_pipe_transport(0) indeed returns a writable transport.

So unless I'm mistaken, I think the word "readable" should be changed to "writable" and vice-versa in the SubprocessTransport.get_pipe_transport documentation.
History
Date User Action Args
2022-01-10 05:59:48xx11mzsetrecipients: + xx11mz, docs@python
2022-01-10 05:59:48xx11mzsetmessageid: <1641794388.21.0.0521440708614.issue46325@roundup.psfhosted.org>
2022-01-10 05:59:48xx11mzlinkissue46325 messages
2022-01-10 05:59:48xx11mzcreate