input() with malformed input stream triggers assertion failure
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
interpreter-core
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40638 |
|---|---|
| Nosy | @tekknolagi |
| 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-05-15.22:17:06.863>
labels = ['interpreter-core', '3.8', '3.7', 'library', '3.9']
title = 'input() with malformed input stream triggers assertion failure'
updated_at = <Date 2020-05-15.22:18:33.456>
user = 'https://github.com/tekknolagi'
bugs.python.org fields:
activity = <Date 2020-05-15.22:18:33.456>
actor = 'tekknolagi'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core', 'Library (Lib)']
creation = <Date 2020-05-15.22:17:06.863>
creator = 'tekknolagi'
dependencies = []
files = []
hgrepos = []
issue_num = 40638
keywords = ['patch']
message_count = 1.0
messages = ['368982']
nosy_count = 1.0
nosy_names = ['tekknolagi']
pr_nums = ['20125']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue40638'
versions = ['Python 3.6', '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
Start by reviewing PR #20125 and reproducing the assertion failure in input() with a malformed input stream. Check the behavior across the Python 3.6–3.9 versions listed in the issue; done means the malformed stream no longer triggers an assertion failure.
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
- Mostly clear
- Newbie friendliness
- 25/100