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 pitrou
Recipients docs@python, lcampagn, neologix, pitrou
Date 2011-07-04.17:07:20
SpamBayes Score 0.00023620234
Marked as misclassified No
Message-id <1309799241.29.0.105010421715.issue12488@psf.upfronthosting.co.za>
In-reply-to
Content
Well, I think it deserves a comment in the documentation that behaviour of Pipes and Queues when one of the process terminates is undefined and implementation-dependent.

By the way, there's internal support in 3.3 to reliably detect killed children, and it's used by concurrent.futures: http://docs.python.org/dev/library/concurrent.futures.html#concurrent.futures.BrokenProcessPool. However, I'm not sure there's an easy way to detect a killed master process from one of the worker processes.
History
Date User Action Args
2011-07-04 17:07:21pitrousetrecipients: + pitrou, neologix, docs@python, lcampagn
2011-07-04 17:07:21pitrousetmessageid: <1309799241.29.0.105010421715.issue12488@psf.upfronthosting.co.za>
2011-07-04 17:07:20pitroulinkissue12488 messages
2011-07-04 17:07:20pitroucreate