gh-145854: Replace DELETE_NAME with PUSH_NULL; STORE_NAME#146006
Conversation
Changes - Removed `DELETE_NAME` - When `STORE_NAME` receives a `NULL` value, it corresponds with deletion
|
I am not sure why three of the CIFuzz tests fail. If anyone could help, that would be appreciated. |
|
This will need a magic number bump (as do all changes that add or remove opcodes) |
markshannon
left a comment
There was a problem hiding this comment.
Looks good. Thanks for doing this.
|
@markshannon A gentle reminder about this PR. |
There are merge conflicts. |
|
Sorry for leaving this sitting for so long. I notice that |
Documentation build overview
254 files changed ·
|
|
@markshannon A reminder about this PR, whenever you get a chance |
markshannon
left a comment
There was a problem hiding this comment.
Looks good. Thanks for doing this.
I mistake in the magic number comment and needs merge conflicts fixing.
Otherwise, good to merge.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Co-authored-by: Mark Shannon <Mark.Shannon@arm.com>
|
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. |
Changes
DELETE_NAMESTORE_NAMEreceives aNULLvalue, it corresponds with deletionDELETE_NAMEinstruction #145854📚 Documentation preview 📚: https://cpython-previews--146006.org.readthedocs.build/