-
-
Notifications
You must be signed in to change notification settings - Fork 29.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PEP 695: Name mangling leaks to surrounding scope #119395
Labels
3.12
bugs and security fixes
3.13
bugs and security fixes
3.14
new features, bugs and security fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
type-bug
An unexpected behavior, bug, or error
Comments
JelleZijlstra
added a commit
to JelleZijlstra/cpython
that referenced
this issue
May 23, 2024
JelleZijlstra
added a commit
to JelleZijlstra/cpython
that referenced
this issue
May 28, 2024
…on#119464) Fixes python#119311. Fixes python#119395. (cherry picked from commit a9a74da)
JelleZijlstra
added a commit
to JelleZijlstra/cpython
that referenced
this issue
May 28, 2024
python#119464) Fixes python#119311. Fixes python#119395. (cherry picked from commit a9a74da)
JelleZijlstra
added a commit
that referenced
this issue
May 28, 2024
estyxx
pushed a commit
to estyxx/cpython
that referenced
this issue
Jul 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
3.12
bugs and security fixes
3.13
bugs and security fixes
3.14
new features, bugs and security fixes
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
type-bug
An unexpected behavior, bug, or error
Bug report
The PEP 695 implementation of generic classes turns on name mangling for the type parameter scope, but never turns it off afterwards. As a result, all code that appears syntactically after the PEP 695 scope also gets mangling applied to it.
I have a fix for this, but I believe applying it requires updating the magic number, and I'm not sure we can afford to to do that on the 3.12 branch.
Linked PRs
The text was updated successfully, but these errors were encountered: