Two Ctrl+C is required to terminate when a pipe is blocking
Open
Nobody has claimed this yet.
extension-modules
topic-IO
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39792 |
|---|---|
| Nosy | @msakai |
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-02-29.06:04:20.472>
labels = ['3.8', 'type-bug', '3.7', '3.9', 'expert-IO']
title = 'Two Ctrl+C is required to terminate when a pipe is blocking'
updated_at = <Date 2020-03-07.09:42:03.441>
user = 'https://github.com/msakai'
bugs.python.org fields:
activity = <Date 2020-03-07.09:42:03.441>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2020-02-29.06:04:20.472>
creator = 'msakai'
dependencies = []
files = []
hgrepos = []
issue_num = 39792
keywords = []
message_count = 1.0
messages = ['362964']
nosy_count = 1.0
nosy_names = ['msakai']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39792'
versions = ['Python 3.7', 'Python 3.8', '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
No source files, tests, or entry points are named. Start by reproducing the blocking-pipe behavior described in the issue and then trace CPython's IO and signal-handling paths; done means a single Ctrl+C terminates the affected operation, with coverage for the regression.
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
- 42/100