-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
bpo-44313: generate LOAD_ATTR/CALL_FUNCTION for top-level imported objects #26677
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
86f2a4d
to
c7c708c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great. Just two very minor issues.
Misc/NEWS.d/next/Core and Builtins/2021-06-10-16-10-39.bpo-44313.34RjI8.rst
Outdated
Show resolved
Hide resolved
When you're done making the requested changes, leave the comment: |
I have made the requested changes; please review again |
Thanks for making the requested changes! @markshannon: please review the changes made to this pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now.
Sorry I missed your update, so importlib needs updating again.
Okay will regenerate them tomorrow. |
🤖 New build scheduled with the buildbot fleet by @isidentical for commit ab1b6c1 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
Thanks. |
@@ -360,6 +360,7 @@ def _write_atomic(path, data, mode=0o666): | |||
# Python 3.11a1 3455 (add MAKE_CELL bpo-43693) | |||
# Python 3.11a1 3456 (interleave cell args bpo-43693) | |||
# Python 3.11a1 3457 (Change localsplus to a bytes object bpo-43693) | |||
# Python 3.11a1 3458 (imported objects now don't use LOAD_METHOD/CALL_METHOD) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't the actual number be bumped below? I don't think it matters much in this case, but for the sake of consistency/clarity for the next bump, it might be good to fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, probably got away during rebase. Will fix
https://bugs.python.org/issue44313