-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
bpo-40870: Invalidate usage of some constants with ast.Name #20649
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
Conversation
Misc/NEWS.d/next/Core and Builtins/2020-06-05-12-48-28.bpo-40870.9cd2sk.rst
Outdated
Show resolved
Hide resolved
…70.9cd2sk.rst Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
@isidentical: Status check is done, and it's a success ✅ . |
Thanks @isidentical for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9. |
GH-20675 is a backport of this pull request to the 3.9 branch. |
GH-20676 is a backport of this pull request to the 3.8 branch. |
@pablogsal the backports passed tests and are ready to merge, but need coredev approval. I don't know if the automerge label is supposed to be carried back or not, but it was not. |
Thanks @terryjreedy for the ping. I have merged the backports :) |
@isidentical , @pablogsal: Is it clear that this should be backported to 3.8? This will break some programs out in the wild unexpectedly. While I don't know the discussion leading to this PR (I suppose that In particular, I encountered this for https://github.com/beetbox/beets/ which uses |
certainly in 3.9, currently also backported to 3.8: python/cpython#20649
Yes, is a bug.
Although we do our best to reduce breakage, the |
new in 3.10, also backported to 3.8 and 3.9: python/cpython#20649 In fact, our generation of some Literals has been invalid since Python 3.4, fix that too.
new in 3.10, also backported to 3.8 and 3.9: python/cpython#20649 In fact, our generation of some Literals has been invalid since Python 3.4, fix that too.
https://bugs.python.org/issue40870