Message131995
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? |
|
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: <1300982953.31.0.459888649279.issue11663@psf.upfronthosting.co.za> |
2011-03-24 16:09:12 | pitrou | link | issue11663 messages |
2011-03-24 16:09:12 | pitrou | create | |
|