Error in multiprocessing.Pool's initializer doesn't stop execution
Open
Nobody has claimed this yet.
3.9 (EOL)
docs
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 43306 |
|---|---|
| Nosy | @terryjreedy, @pitrou, @applio, @athompson673 |
| 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 2021-02-23.15:55:10.770>
labels = ['type-bug', 'library', '3.9', 'docs']
title = "Error in multiprocessing.Pool's initializer doesn't stop execution"
updated_at = <Date 2021-08-23.18:43:57.347>
user = 'https://bugs.python.org/nemeskeyd'
bugs.python.org fields:
activity = <Date 2021-08-23.18:43:57.347>
actor = 'athompson6735'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2021-02-23.15:55:10.770>
creator = 'nemeskeyd'
dependencies = []
files = ['50230']
hgrepos = []
issue_num = 43306
keywords = []
message_count = 4.0
messages = ['387577', '387763', '400150', '400161']
nosy_count = 6.0
nosy_names = ['terry.reedy', 'pitrou', 'docs@python', 'nemeskeyd', 'davin', 'athompson6735']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue43306'
versions = ['Python 3.9']
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 uploaded pool.py reproduction and the multiprocessing.Pool initializer behavior described in the issue. Read how the reported initializer error is handled, then verify the intended stopping behavior and use that behavior as the completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100