Ross Lagerwall <rosslagerw...@gmail.com> added the comment: The docs should be updated. This has been noted in msg54949 and http://www.enricozini.org/2009/debian/python-pipes/
Perhaps this example will make it clear: import subprocess p1 = subprocess.Popen(["yes"], stdout=subprocess.PIPE) p2 = subprocess.Popen(["head"], stdin=p1.stdout, stdout=subprocess.PIPE) #p1.stdout.close() p1.wait() This example hangs. "yes" writes to "head" and head reads the first 10 lines and then exits. But, "yes" does not receive a SIGPIPE because the python process still has a p1.stdout open. Thus, p1.stdout should be closed after being passed to p2. ---------- nosy: +rosslagerwall _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7678> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
