Commit c4634bf
doc: update subprocess.killed
This commit changes the wording of subprocess.killed to reflect
that a child process was successfully signaled, and not
necessarily terminated.
Fixes: #16747
PR-URL: #16748
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>1 parent 8d31294 commit c4634bf
1 file changed
Lines changed: 4 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -1048,10 +1048,11 @@ added: v0.5.10 | |||
| 1048 | 1048 | --> | |
| 1049 | 1049 | ||
| 1050 | 1050 | * {boolean} Set to `true` after `subprocess.kill()` is used to successfully | |
| 1051 | - terminate the child process. | ||
| 1051 | + send a signal to the child process. | ||
| 1052 | 1052 | ||
| 1053 | - The `subprocess.killed` property indicates whether the child process was | ||
| 1054 | - successfully terminated using `subprocess.kill()`. | ||
| 1053 | + The `subprocess.killed` property indicates whether the child process | ||
| 1054 | + successfully received a signal from `subprocess.kill()`. The `killed` property | ||
| 1055 | + does not indicate that the child process has been terminated. | ||
| 1055 | 1056 | ||
| 1056 | 1057 | <a name="child_process_child_pid"></a> | |
| 1057 | 1058 | ### subprocess.pid | |
0 commit comments