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 pakal
Recipients ocean-city, pakal
Date 2009-03-05.21:23:00
SpamBayes Score 6.4408204e-07
Marked as misclassified No
Message-id <1236288184.48.0.698516141742.issue4192@psf.upfronthosting.co.za>
In-reply-to
Content
Thansk a lot for reviewing the problem

Indeed, "p.wait()" seems to do the trick in this case.

Is there any global way to avoid such pipe problems ? I mean, in any
case, one end of each pipe has to be closed before the other end, so
such errors might occur with the child process' stdin (in case the child
dies first and the parent flushes then its pipe toward the child's
stdin) or with its stdout (if the parent dies first and the child
flushes then its stdout). 

Or are we sure that there won't be errors as long as children die before
the parent process ?
History
Date User Action Args
2009-03-05 21:23:04pakalsetrecipients: + pakal, ocean-city
2009-03-05 21:23:04pakalsetmessageid: <1236288184.48.0.698516141742.issue4192@psf.upfronthosting.co.za>
2009-03-05 21:23:02pakallinkissue4192 messages
2009-03-05 21:23:01pakalcreate