Improve error messages for non-matching `elif`/`else` statements
Open
Nobody has claimed this yet.
interpreter-core
topic-parser
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 45759 |
|---|---|
| Nosy | @aroberge, @lysnikolaou, @pablogsal, @AlexWaygood, @thatbirdguythatuknownot |
| 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 2021-11-08.23:51:38.287>
labels = ['interpreter-core', 'type-bug', '3.10', '3.11']
title = 'Improve error messages for non-matching `elif`/`else` statements'
updated_at = <Date 2021-11-25.12:15:15.681>
user = 'https://github.com/thatbirdguythatuknownot'
bugs.python.org fields:
activity = <Date 2021-11-25.12:15:15.681>
actor = 'Crowthebird'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Parser']
creation = <Date 2021-11-08.23:51:38.287>
creator = 'Crowthebird'
dependencies = []
files = []
hgrepos = []
issue_num = 45759
keywords = ['patch']
message_count = 2.0
messages = ['405990', '405997']
nosy_count = 5.0
nosy_names = ['aroberge', 'lys.nikolaou', 'pablogsal', 'AlexWaygood', 'Crowthebird']
pr_nums = ['29481', '29513', '29775']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45759'
versions = ['Python 3.10', 'Python 3.11']
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 Parser component and review PRs #29481, #29513, and #29775 to understand the proposed handling of non-matching elif/else statements. The work is done when these cases produce improved, more specific error messages and the existing parser behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100