➜

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 Albert.Strasheim, aljungberg, asksol, bquinlan, gdb, gkcn, hongqn, jnoller, pitrou, vlasovskikh, vstinner
Date 2011-05-03.11:15:35
SpamBayes Score 3.9524602e-05
Marked as misclassified No
Message-id <1304421327.3567.1.camel@localhost.localdomain>
In-reply-to <1304421085.63.0.965002749198.issue9205@psf.upfronthosting.co.za>
Content 
> Under what circumstances do we expect a ProcessPoolExecutor child
> process to be killed outside of the control of the
> ProcessPoolExecutor?

Killed by the user, or by an automatic device (such as the Linux OOM
killer), or crashed.

> If the user kills a child then maybe all we want to do is raise an
> exception rather than deadlock as a convenience.

That's what the patch does, roughly.
History
Date User Action Args
2011-05-03 11:15:36pitrousetrecipients: + pitrou, bquinlan, vstinner, jnoller, hongqn, asksol, vlasovskikh, gdb, Albert.Strasheim, aljungberg, gkcn
2011-05-03 11:15:36pitroulinkissue9205 messages
2011-05-03 11:15:35pitroucreate