Confusing error messages for %-formatting, related to escaped %-characters
Open
Nobody has claimed this yet.
docs
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39486 |
|---|---|
| Nosy | @cfbolz, @serhiy-storchaka, @iritkatriel |
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-01-29.14:49:09.257>
labels = ['interpreter-core', 'type-bug', '3.11']
title = 'Confusing error messages for %-formatting, related to escaped %-characters'
updated_at = <Date 2022-01-28.20:04:26.600>
user = 'https://github.com/cfbolz'
bugs.python.org fields:
activity = <Date 2022-01-28.20:04:26.600>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-01-29.14:49:09.257>
creator = 'Carl.Friedrich.Bolz'
dependencies = []
files = []
hgrepos = []
issue_num = 39486
keywords = []
message_count = 4.0
messages = ['360965', '360974', '360977', '412029']
nosy_count = 4.0
nosy_names = ['Carl.Friedrich.Bolz', 'SilentGhost', 'serhiy.storchaka', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39486'
versions = ['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 by reviewing the linked BPO issue 39486 and its discussion about %-formatting and escaped percent characters. The payload names no source file, test, or reproduction cases, so the expected error-message changes and completion criteria need to be established before implementation.
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
- Needs clarification
- Newbie friendliness
- 25/100