diff options
author | Batuhan Taşkaya <47358913+isidentical@users.noreply.github.com> | 2020-03-15 22:45:56 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-03-15 19:45:56 +0000 |
commit | ac10e0c93218627d1a639db0b7b41714c5f6a883 (patch) | |
tree | e736b856ff7c84113e035e67389d8246e177a859 /Python/Python-ast.c | |
parent | c81609e44eed641d3b8a137daa31ef35501c1f85 (diff) | |
download | cpython-git-ac10e0c93218627d1a639db0b7b41714c5f6a883.tar.gz |
bpo-39360: Ensure all workers exit when finalizing a multiprocessing Pool (GH-19009)
When the pull is not used via the context manager or terminate() is called, there is a system in multiprocessing.util that handles finalization of all pools via an atexit handler (the Finalize) class. This class registers the _terminate_pool handler in the registry of finalizers of the module, and that registry is called on interpreter exit via _exit_function. The problem is that the "happy" path with the context manager or manual call to finalize() does some extra steps that _terminate_pool does not. The step that is not executed when the atexit() handler calls _terminate_pool is pinging the _change_notifier queue to unblock the maintenance threads.
This commit moves the notification to the _terminate_pool function so is called from both code paths.
Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
Diffstat (limited to 'Python/Python-ast.c')
0 files changed, 0 insertions, 0 deletions