pool worker can't be terminated
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42849 |
|---|---|
| Nosy | @terryjreedy, @pitrou, @pppery, @applio |
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-01-07.04:00:06.820>
labels = ['3.7', 'type-bug', 'library']
title = "pool worker can't be terminated"
updated_at = <Date 2021-01-15.21:53:53.632>
user = 'https://bugs.python.org/huangzhesi'
bugs.python.org fields:
activity = <Date 2021-01-15.21:53:53.632>
actor = 'ppperry'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-01-07.04:00:06.820>
creator = 'huangzhesi'
dependencies = []
files = []
hgrepos = []
issue_num = 42849
keywords = []
message_count = 3.0
messages = ['384560', '384698', '385126']
nosy_count = 5.0
nosy_names = ['terry.reedy', 'pitrou', 'ppperry', 'davin', 'huangzhesi']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42849'
versions = ['Python 3.7']
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 linked bugs.python.org issue 42849 and review its three messages, since the migrated issue provides no reproduction, files, or tests. Determine how the pool worker fails to terminate and establish a reproducible case before identifying the relevant Library (Lib) area; done means the reported worker can be terminated as expected.
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
- 20/100