This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Pablo.Bitton
Recipients Pablo.Bitton, abbot, astrand, belopolsky, brian.curtin, dmalcolm, filippo, gd2shoe, giampaolo.rodola, guettli, matthieu.labbe, orsenthil, pitrou, r.david.murray, ragnar, rnk, srid
Date 2010-08-08.16:07:32
SpamBayes Score 6.118295e-11
Marked as misclassified No
Message-id <1281283659.24.0.851753333351.issue5673@psf.upfronthosting.co.za>
In-reply-to
Content
I'd like to report a problem I encountered with the discussed use pattern using subprocess-timeout-v5.patch on linux. I don't have python3 installed at work, sorry.

When running:
p = subprocess.Popen("tcpdump -i eth0 > file &", stdin=subprocess.PIPE, stdout=subprocess.PIPE, stderr=subprocess.PIPE, shell=True, universal_newlines=True)
try:
    out, err = p.communicate(timeout=1)
except subprocess.TimeoutExpired:
    p.kill()
    out, err = p.communicate()

After the timeout happens, the last line raises a ValueError: I/O operation on closed file.

The exception is thrown from the register_and_append call for self.stdout in _communicate_with_poll. I'm sorry again for not being able to attach the full traceback.

The problem doesn't reproduce without the '&' or the '> file', and doesn't reproduce with other executables I've tried.
History
Date User Action Args
2010-08-08 16:07:39Pablo.Bittonsetrecipients: + Pablo.Bitton, guettli, astrand, belopolsky, orsenthil, pitrou, ragnar, giampaolo.rodola, abbot, gd2shoe, r.david.murray, brian.curtin, rnk, srid, matthieu.labbe, dmalcolm, filippo
2010-08-08 16:07:39Pablo.Bittonsetmessageid: <1281283659.24.0.851753333351.issue5673@psf.upfronthosting.co.za>
2010-08-08 16:07:32Pablo.Bittonlinkissue5673 messages
2010-08-08 16:07:32Pablo.Bittoncreate