[issue1344] subprocess.communication doc could use clarification

2007-11-24 Thread Georg Brandl

Georg Brandl added the comment:

Thanks, this is now documented (r59164).

--
nosy: +georg.brandl
status: open - closed

__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1344
__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue1344] subprocess.communication doc could use clarification

2007-10-27 Thread Dean Sturtevant

New submission from Dean Sturtevant:

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)

--
components: Documentation
messages: 56858
nosy: dsturtevant
severity: normal
status: open
title: subprocess.communication doc could use clarification
versions: Python 2.5

__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1344
__
___
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com