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

STINNER Victor added the comment: This issue is a duplicate of #9205. -- resolution: -> duplicate status: open -> closed ___ Python tracker ___

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

STINNER Victor added the comment: It's possible to stop the parent with a CTRL+c, and so here is the trace of blocking function: $ ./python y.py parent 26706: wait child child 26707: wait 60 seconds ^CProcess PoolWorker-2: Traceback (most recent call last): File "y.py", line 13, in Traceba

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

Changes by STINNER Victor : -- title: concurrent.futures (or multiprocessing?) doesn't detect killed processes -> multiprocessing (and concurrent.futures) doesn't detect killed processes ___ Python tracker ___