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 rnk
Recipients Pablo.Bitton, abbot, astrand, belopolsky, brian.curtin, dmalcolm, filippo, gd2shoe, giampaolo.rodola, guettli, matthieu.labbe, orsenthil, pitrou, r.david.murray, ragnar, rnk, srid, tim.golden
Date 2011-01-06.22:13:25
SpamBayes Score 3.124789e-07
Marked as misclassified No
Message-id <1294352021.29.0.464027485365.issue5673@psf.upfronthosting.co.za>
In-reply-to
Content
Pablo, so if I understand the issue you've run into correctly, you are using shell redirection to redirect stdout to a file, and then attempting to read from it using stdout=subprocess.PIPE.

It seems to me like this behavior is expected, because the shell will close it's current stdout file descriptor and open a new one pointing at "file".  When python tries to read from its end of the pipe, it complains that the fd has been closed.

I can avoid the problem here either by not reading stdout or by not redirecting to a file.
History
Date User Action Args
2011-01-06 22:13:41rnksetrecipients: + rnk, guettli, astrand, belopolsky, orsenthil, pitrou, ragnar, giampaolo.rodola, tim.golden, abbot, gd2shoe, r.david.murray, brian.curtin, srid, matthieu.labbe, dmalcolm, filippo, Pablo.Bitton
2011-01-06 22:13:41rnksetmessageid: <1294352021.29.0.464027485365.issue5673@psf.upfronthosting.co.za>
2011-01-06 22:13:25rnklinkissue5673 messages
2011-01-06 22:13:25rnkcreate