Gregory P. Smith g...@krypto.org added the comment:
documentation updated in r88352. thanks!
--
assignee: docs@python - gregory.p.smith
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
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 =
Éric Araujo mer...@netwok.org added the comment:
As a non-expert user of subprocess, calling close before communicate seems
strange to me. Does the example code with a bug work if close is called after
communicate?
In the 3.2 docs, we could update the example to use a with statement, unless
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
assignee: georg.brandl - d...@python
nosy: +d...@python
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7678
___
New submission from Steven K. Wong slid...@hotmail.com:
The example code at
http://www.python.org/doc/2.6.2/library/subprocess.html#replacing-shell-pipeline
should be updated to add the close() call noted below:
output=`dmesg | grep hda`
==
p1 = Popen([dmesg], stdout=PIPE)
p2 = Popen([grep,
