Improve ``NameError`` message when non-mangled name exists in the global scope
Open
Nobody has claimed this yet.
interpreter-core
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
Here is the code:
def __a():
print("A")
class A:
def b(self):
__a()
a = A()
a.b()
It was expected to show a short message "A". However, I got a NameError:
❯ python3.12 bug\ represent.py
Traceback (most recent call last):
File "/home/PC-Killer/python_work/Demos/bug represent.py", line 11, in <module>
a.b()
File "/home/PC-Killer/python_work/Demos/bug represent.py", line 7, in b
__a()
^^^
NameError: name '_A__a' is not defined
❯ python3.13 bug\ represent.py
Traceback (most recent call last):
File "/home/PC-Killer/python_work/Demos/bug represent.py", line 11, in <module>
a.b()
~~~^^
File "/home/PC-Killer/python_work/Demos/bug represent.py", line 7, in b
__a()
^^^
NameError: name '_A__a' is not defined
It seems that the name had been translated in an unexpected way.
CPython versions tested on:
3.12, 3.13
Operating systems tested on:
Linux
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
Run the provided bug represent.py reproducer with the reported Python versions. No CPython source file or test is named, so locate the existing name-mangling and NameError suggestion tests and trace their entry points. Done means the example produces the intended concise message without regressing related NameError behavior.
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
- 38/100