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 simon3z
Recipients dmalcolm, pitrou, simon3z
Date 2011-01-24.17:08:01
SpamBayes Score 3.2474847e-05
Marked as misclassified No
Message-id <1295888885.72.0.303452120308.issue10963@psf.upfronthosting.co.za>
In-reply-to
Content
I agree they are orthogonal. The problem is that Popen.communicate doesn't support a way to ignore the exception and keep reading from stdout and sterr until the process dies.
When the child closes the stdin its (error/debug/info) messages on stout/sterr will be lost.
I am not just concerned about checking both the return-code and this exception, I am also worried about losing important information.
History
Date User Action Args
2011-01-24 17:08:05simon3zsetrecipients: + simon3z, pitrou, dmalcolm
2011-01-24 17:08:05simon3zsetmessageid: <1295888885.72.0.303452120308.issue10963@psf.upfronthosting.co.za>
2011-01-24 17:08:01simon3zlinkissue10963 messages
2011-01-24 17:08:01simon3zcreate