multiprocessing.Connection.poll raises BrokenPipeError on Windows
Open
Nobody has claimed this yet.
3.9 (EOL)
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41008 |
|---|---|
| Nosy | @zanchey |
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 2020-06-17.14:59:25.730>
labels = ['type-bug', '3.9']
title = 'multiprocessing.Connection.poll raises BrokenPipeError on Windows'
updated_at = <Date 2020-06-17.14:59:25.730>
user = 'https://github.com/zanchey'
bugs.python.org fields:
activity = <Date 2020-06-17.14:59:25.730>
actor = 'zanchey'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2020-06-17.14:59:25.730>
creator = 'zanchey'
dependencies = []
files = []
hgrepos = []
issue_num = 41008
keywords = []
message_count = 1.0
messages = ['371748']
nosy_count = 1.0
nosy_names = ['zanchey']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41008'
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 at the multiprocessing.Connection.poll entry point and reproduce the reported behavior on Windows. Trace why polling raises BrokenPipeError, then verify that polling a broken connection behaves as intended without introducing regressions. The issue provides no source file or test location, so locating the implementation and relevant tests is part of the initial investigation.
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
- 30/100