tty unblocking setraw and save-restore features
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40229 |
|---|---|
| Nosy | @StevenLu2004 |
| PRs |
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-04-08.17:44:06.826>
labels = ['3.7', 'type-bug', 'library']
title = 'tty unblocking setraw and save-restore features'
updated_at = <Date 2020-04-08.17:47:31.816>
user = 'https://github.com/StevenLu2004'
bugs.python.org fields:
activity = <Date 2020-04-08.17:47:31.816>
actor = 'python-dev'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-04-08.17:44:06.826>
creator = 'Steven Lu'
dependencies = []
files = []
hgrepos = []
issue_num = 40229
keywords = ['patch']
message_count = 1.0
messages = ['365996']
nosy_count = 2.0
nosy_names = ['python-dev', 'Steven Lu']
pr_nums = ['19440']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue40229'
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 by reviewing the linked pull request #19440 and the tty-related issue history. The payload names no files or tests, so use the existing proposal to determine the intended unblocking, setraw, and save-restore behavior; done means completing and validating that work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100