New submission from Antoine Pitrou <pit...@free.fr>: 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? ---------- components: Library (Lib) messages: 131995 nosy: asksol, bquinlan, jnoller, pitrou priority: normal severity: normal status: open title: concurrent.futures (or multiprocessing?) doesn't detect killed processes versions: Python 3.2, Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11663> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
