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.

classification
Title: Documentation for SubprocessTransport.get_pipe_transport return values readable/writable
Type: Stage:
Components: Documentation Versions: Python 3.11, Python 3.10, Python 3.9, Python 3.8, Python 3.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, xx11mz
Priority: normal Keywords:

Created on 2022-01-10 05:59 by xx11mz, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg410188 - (view) Author: xx11mz (xx11mz) Date: 2022-01-10 05:59
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-04-11 14:59:54adminsetgithub: 90483
2022-01-10 05:59:48xx11mzcreate