[docs] [issue25511] multiprocessing pool blocks SIGTERM from being handled

David Jones report at bugs.python.org
Thu Oct 29 11:28:51 EDT 2015

New submission from David Jones:

This is probably related to #21913, but more specifically concerns the documentation. I have a sub process of a larger program that handles a SIGTERM sent by the main process for a clean shutdown. However, if I launch a parallel task in the sub process, via multiprocessing.Pool.imap_unordered, all signals are blocked until pool finishes running the task. 

If this isn't going to be fixed, then it ought to at least be clearly documented. It took a very long time to diagnose this problem. It requires a programmer to understand the underlying implementation of a high-level construct, thus defeating the purpose of using a high level construct.

Also, is there a way to work around this?

assignee: docs at python
components: Documentation
messages: 253678
nosy: djones, docs at python
priority: normal
severity: normal
status: open
title: multiprocessing pool blocks SIGTERM from being handled
type: behavior
versions: Python 2.7

Python tracker <report at bugs.python.org>

More information about the docs mailing list