-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-63891: Rename Py_SAFE_DOWNCAST to _Py_DOWNCAST #15090
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
cc @pitrou |
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.
Not very sure if renaming this would be a good idea and what impact it can have. 🤷♂
But I'd like to see the discussion on bug tracker regarding this. Overall the changes look okay to me.
Thanks for review, Sanyam. Waiting enough discussion :) |
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.
You cannot remove Py_SAFE_DOWNCAST() macro which is part of the Python stable C ABI.
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 |
Hi, victor. ps: docs need updated too. |
You PR says:
So it removes Py_SAFE_DOWNCAST() macro. Compilation of any C extension using Py_SAFE_DOWNCAST() will fail with this change.
That would be an option. |
Thanks, victor. I add an alias of |
Ops, catching an typo erro incidentally: #16230 |
I have made the requested changes; please review again |
Thanks for making the requested changes! @vstinner: please review the changes made to this pull request. |
I'm +0. Removed me from reviewers. |
Closing, as the linked issue is closed. |
https://bugs.python.org/issue19692