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 ggenellina
Recipients amy20_z, belopolsky, ggenellina, lemur, vstinner
Date 2008-12-15.23:24:00
SpamBayes Score 1.3304972e-07
Marked as misclassified No
Message-id <>
I think communicate() works as documented now: reads stdout/stderr 
until EOF, *and* waits for subprocess to terminate.

You're asking for a different method, or perhaps an optional 
parameter "return_when_died" to communicate, so it returns as soon as 
the child process terminates (I don't like the parameter name...)

I think this is more a feature request than a crash, targeted to 
2.7/3.1 - 2.4 only gets security fixes anyway.
Date User Action Args
2008-12-15 23:25:20ggenellinasetrecipients: + ggenellina, belopolsky, vstinner, amy20_z, lemur
2008-12-15 23:25:20ggenellinasetmessageid: <>
2008-12-15 23:24:01ggenellinalinkissue4216 messages
2008-12-15 23:24:00ggenellinacreate