➜
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.
Created on 2007-10-27 17:15 by dsturtevant, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg56858 - (view) | Author: Dean Sturtevant (dsturtevant) | Date: 2007-10-27 17:15 | |
It would be helpful for the documentation for subprocess.communicate to point out that when Popening a process, stdin=PIPE needs to be set if the input parameter to communicate is to have any meaning. Similary, stdout=PIPE and stderr=PIPE need to be set in order for the respective component of the return value not to be None. That is, if that is indeed correct (I observed this using Python 2.5 (r25:51908, Sep 19 2006, 09:52:17) [MSC v.1310 32 bit (Intel)] on win32) |
|||
| msg57801 - (view) | Author: Georg Brandl (georg.brandl) *  |
Date: 2007-11-24 11:32 | |
Thanks, this is now documented (r59164). |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:27 | admin | set | github: 45685 |
| 2007-11-24 11:32:22 | georg.brandl | set | status: open -> closed nosy: + georg.brandl messages: + msg57801 |
| 2007-10-27 17:15:09 | dsturtevant | create | |