Unicode-mangled names refer inconsistently to constants
Open
Nobody has claimed this yet.
3.9 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 46555 |
|---|---|
| Nosy | @cfbolz, @serhiy-storchaka, @eryksun, @Kodiologist, @jack1142, @snoopjedi |
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 2022-01-27.21:57:22.495>
labels = ['type-bug', '3.9']
title = 'Unicode-mangled names refer inconsistently to constants'
updated_at = <Date 2022-02-01.00:41:18.436>
user = 'https://github.com/Kodiologist'
bugs.python.org fields:
activity = <Date 2022-02-01.00:41:18.436>
actor = 'SnoopJeDi'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2022-01-27.21:57:22.495>
creator = 'Kodiologist'
dependencies = []
files = []
hgrepos = []
issue_num = 46555
keywords = []
message_count = 8.0
messages = ['411930', '412070', '412071', '412150', '412167', '412169', '412170', '412226']
nosy_count = 6.0
nosy_names = ['Carl.Friedrich.Bolz', 'serhiy.storchaka', 'eryksun', 'Kodiologist', 'jack1142', 'SnoopJeDi']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue46555'
versions = ['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 reading the linked bugs.python.org issue 46555 and its discussion, then identify which Python name-mangling behavior causes constants to be referenced inconsistently. The issue provides no source files or tests, so the affected implementation and regression coverage must be located before defining completion.
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