Message262871
Even if we can’t agree on any behaviour change, I think it might be worth documenting how these functions behave on exceptions (interrupts) other than TimeoutExpired. Currently all I can find is “If the timeout expires, the child process will be killed and waited for.” I think this could be expanded to also say what happens if the parent is interrupted by a signal such as KeyboardInterrupt:
* Current behaviour: Immediately kill child (i.e. timeout expiry is not special)
* Previous behaviour: Return without waiting for child, which will become a zombie
* Mike’s proposal: Wait indefinitely for child without killing it, which could defeat the purpose of the timeout, especially if the child ignores or does not receive the same signal as the parent |
|
Date |
User |
Action |
Args |
2016-04-04 21:03:23 | martin.panter | set | recipients:
+ martin.panter, vstinner, SilentGhost, Mike Pomraning, rpcope1 |
2016-04-04 21:03:23 | martin.panter | set | messageid: <1459803803.36.0.564276369277.issue25942@psf.upfronthosting.co.za> |
2016-04-04 21:03:23 | martin.panter | link | issue25942 messages |
2016-04-04 21:03:22 | martin.panter | create | |
|