Author eryksun
Recipients Leonardo Francalanci, eryksun, martin.panter, r.david.murray
Date 2017-09-14.07:53:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1505375583.8.0.998280704893.issue31447@psf.upfronthosting.co.za>
In-reply-to
Content
> Now I can read from the "R" pipes with 0 problems (getting the error 
> and output streams)

The pipe handles are inherited by waitfor.exe, just as before. You'll find that reading to EOF will block just as it does when using subprocess.PIPE with communicate(). For example:

    stderr = open(errPipeR, 'r')
    err = stderr.read()

The above stderr.read() will return when waitfor.exe either exits or gets terminated.

> and proc.communicate exits as soon as the called process exits 
> (4 seconds).

proc.stdout and proc.stderr are None in this case, so all communicate() can do is write to proc.stdin, if there's input text, and then wait() for the process to exit.
History
Date User Action Args
2017-09-14 07:53:03eryksunsetrecipients: + eryksun, r.david.murray, martin.panter, Leonardo Francalanci
2017-09-14 07:53:03eryksunsetmessageid: <1505375583.8.0.998280704893.issue31447@psf.upfronthosting.co.za>
2017-09-14 07:53:03eryksunlinkissue31447 messages
2017-09-14 07:53:03eryksuncreate