Message 131995 - Python tracker

➜

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	asksol, bquinlan, jnoller, pitrou
Date	2011-03-24.16:09:12
SpamBayes Score	8.847063e-06
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
If you do: ./python -c "from concurrent.futures import ; from time import ; t = ProcessPoolExecutor(1); t.submit(sleep, 60)" and then kill the child process, the parent process doesn't notice and waits endlessly for the child to return the results. I'm using concurrent.futures here but I assume the bug (or limitation) is on the multiprocessing side?

If you do:

./python -c "from concurrent.futures import *; from time import *; t = ProcessPoolExecutor(1); t.submit(sleep, 60)"

and then kill the child process, the parent process doesn't notice and waits endlessly for the child to return the results.

I'm using concurrent.futures here but I assume the bug (or limitation) is on the multiprocessing side?

History
Date	User	Action	Args
2011-03-24 16:09:13	pitrou	set	recipients: + pitrou, bquinlan, jnoller, asksol
2011-03-24 16:09:13	pitrou	set	messageid: <[email protected]>
2011-03-24 16:09:12	pitrou	link	issue11663 messages
2011-03-24 16:09:12	pitrou	create