Terry J. Reedy tjre...@udel.edu added the comment:
Closing because OP did not disagree with Wong's explanation of why not a bug.
If someone disagreea and wants to reopen, this should be verified and marked
for a current version (2.7+)
--
nosy: +tjreedy
resolution: - invalid
status:
Steven K. Wong slid...@hotmail.com added the comment:
I think the hang is not a bug. Take a look at the Popen documentation on
close_fds. If you specify close_fds=True when creating proc2, the hang will not
happen when you remove the proc2.stdin.close() line.
--
nosy: +steven.k.wong
Steven K. Wong slid...@hotmail.com added the comment:
See this related issue: http://bugs.python.org/issue7448
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5898
___
Steven K. Wong slid...@hotmail.com added the comment:
See this related issue: http://bugs.python.org/issue7213
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5898
___
New submission from François Granade franc...@granade.com:
If I remove the proc2.stdin.close() in the script below, the
proc1.wait() will hang. Tested on MacOS, Linux, CygWin on 2.5.2 and
2.6. Is it a bug ?
from subprocess import Popen, PIPE
proc1 = Popen('cat -', shell=True, stdin=PIPE,
François Granade franc...@granade.com added the comment:
Note that I use this wait(), otherwise, on CygWin, proc1 does not
properly dies, and leaves opened (undeletable - that's windows !) files
around
--
___
Python tracker rep...@bugs.python.org
