Can't gracefully ctrl+C multiprocessing pool on Python3 & Windows
Open
Nobody has claimed this yet.
3.10
3.8 (EOL)
3.9 (EOL)
OS-windows
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 38428 |
|---|---|
| Nosy | @pfmoore, @pitrou, @tjguk, @zware, @eryksun, @zooba, @applio, @rebeccafair |
| 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-10-10.08:35:51.894>
labels = ['3.10', 'type-bug', '3.8', '3.9', 'OS-windows']
title = "Can't gracefully ctrl+C multiprocessing pool on Python3 & Windows"
updated_at = <Date 2021-03-22.03:12:37.354>
user = 'https://github.com/rebeccafair'
bugs.python.org fields:
activity = <Date 2021-03-22.03:12:37.354>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2019-10-10.08:35:51.894>
creator = 'rebeccafair'
dependencies = []
files = ['48653']
hgrepos = []
issue_num = 38428
keywords = []
message_count = 5.0
messages = ['354344', '354346', '354393', '354413', '389273']
nosy_count = 8.0
nosy_names = ['paul.moore', 'pitrou', 'tim.golden', 'zach.ware', 'eryksun', 'steve.dower', 'davin', 'rebeccafair']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38428'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
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 attached bug.py and reproduce the Ctrl+C behavior on Windows with Python 3. Then inspect the multiprocessing Pool paths involved and determine how graceful interruption should be verified; the issue does not name a regression test or implementation file, so completion requires adding or updating appropriate coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100