New submission from xx11mz <xx1...@live.com>:
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. ---------- assignee: docs@python components: Documentation messages: 410188 nosy: docs@python, xx11mz priority: normal severity: normal status: open title: Documentation for SubprocessTransport.get_pipe_transport return values readable/writable versions: Python 3.10, Python 3.11, Python 3.7, Python 3.8, Python 3.9 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46325> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
