[issue11663] concurrent.futures (or multiprocessing?) doesn't detect killed processes

STINNER Victor added the comment: In the following example, the parent doesn't react when the child process is killed: - from os import getpid from time import sleep, time from multiprocessing import Pool def f(sec): print("child %s: wait %s seconds" % (getpid(), sec)) sleep(sec)

[issue11663] concurrent.futures (or multiprocessing?) doesn't detect killed processes

Antoine Pitrou added the comment: Le jeudi 24 mars 2011 à 16:16 +, STINNER Victor a écrit : > STINNER Victor added the comment: > > In the following example, if I kill the child process, the parent is > immediatly done: > --- > from os import getpid > from time import sleep > from multipr

[issue11663] concurrent.futures (or multiprocessing?) doesn't detect killed processes

STINNER Victor added the comment: In the following example, if I kill the child process, the parent is immediatly done: --- from os import getpid from time import sleep from multiprocessing import Process def f(sec): print("child %s: wait %s seconds" % (getpid(), sec)) sleep(sec) if _

[issue11663] concurrent.futures (or multiprocessing?) doesn't detect killed processes

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue11663] concurrent.futures (or multiprocessing?) doesn't detect killed processes

New submission from Antoine Pitrou : 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