Setting a signal handler gets multiprocessing.Pool stuck
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
topic-multiprocessing
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38227 |
|---|---|
| Nosy | @pitrou, @wumpus |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2019-09-19.21:41:35.764>
labels = ['3.8', 'library']
title = 'Setting a signal handler gets multiprocessing.Pool stuck'
updated_at = <Date 2020-07-19.17:38:12.599>
user = 'https://bugs.python.org/ionelmc'
bugs.python.org fields:
activity = <Date 2020-07-19.17:38:12.599>
actor = 'wumpus'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-09-19.21:41:35.764>
creator = 'ionelmc'
dependencies = []
files = ['48615', '49130', '49131']
hgrepos = []
issue_num = 38227
keywords = ['patch']
message_count = 6.0
messages = ['352815', '353938', '353947', '368233', '368234', '368237']
nosy_count = 4.0
nosy_names = ['pitrou', 'ionelmc', 'wumpus', 'mapozyan']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue38227'
versions = ['Python 3.8']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reproduction files mp-bug-python2.8.py and mp-signal-bug-python3.8.py, then inspect pool.py.patch to understand the proposed direction. Reproduce the stuck multiprocessing.Pool behavior and verify that the pool no longer hangs when a signal handler is set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100