Skip to content

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

Closed
wants to merge 3 commits into from

Conversation

shihai1991
Copy link
Member

@shihai1991 shihai1991 commented Aug 3, 2019

@shihai1991
Copy link
Member Author

cc @pitrou

Copy link
Member

@CuriousLearner CuriousLearner left a 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.

@shihai1991
Copy link
Member Author

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 :)

Copy link
Member

@vstinner vstinner left a 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.

@bedevere-bot
Copy link

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 I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

@shihai1991
Copy link
Member Author

Py_SAFE_DOWNCAST

Hi, victor.
Make sure I understand: adding #define _Py_DOWNCAST(VALUE, WIDE, NARROW) Py_SAFE_DOWNCAST(VALUE, WIDE, NARROW) for backwards compatibility and using _Py_DOWNCAST to repalce Py_SAFE_DOWNCAST inside.

ps: docs need updated too.

@vstinner
Copy link
Member

You PR says:

Rename :meth:Py_SAFE_DOWNCAST to :meth:_Py_DOWNCAST

So it removes Py_SAFE_DOWNCAST() macro. Compilation of any C extension using Py_SAFE_DOWNCAST() will fail with this change.

Make sure I understand: adding #define _Py_DOWNCAST(VALUE, WIDE, NARROW) Py_SAFE_DOWNCAST(VALUE, WIDE, NARROW) for backwards compatibility and using _Py_DOWNCAST to repalce Py_SAFE_DOWNCAST inside.

That would be an option.

@shihai1991
Copy link
Member Author

You PR says:

Rename :meth:Py_SAFE_DOWNCAST to :meth:_Py_DOWNCAST

So it removes Py_SAFE_DOWNCAST() macro. Compilation of any C extension using Py_SAFE_DOWNCAST() will fail with this change.

Make sure I understand: adding #define _Py_DOWNCAST(VALUE, WIDE, NARROW) Py_SAFE_DOWNCAST(VALUE, WIDE, NARROW) for backwards compatibility and using _Py_DOWNCAST to repalce Py_SAFE_DOWNCAST inside.

That would be an option.

Thanks, victor. I add an alias of Py_SAFE_DOWNCAST and update the news.

@shihai1991
Copy link
Member Author

Ops, catching an typo erro incidentally: #16230

@shihai1991
Copy link
Member Author

I have made the requested changes; please review again

@bedevere-bot
Copy link

Thanks for making the requested changes!

@vstinner: please review the changes made to this pull request.

@methane
Copy link
Member

methane commented Oct 26, 2020

I'm +0. Removed me from reviewers.

@tiran tiran removed their request for review April 17, 2021 21:15
@rhettinger rhettinger removed their request for review May 3, 2022 06:31
@pitrou pitrou mentioned this pull request Jan 12, 2024
@erlend-aasland erlend-aasland changed the title bpo-19692: Rename Py_SAFE_DOWNCAST to _Py_DOWNCAST gh-63891: Rename Py_SAFE_DOWNCAST to _Py_DOWNCAST Jan 12, 2024
@erlend-aasland
Copy link
Contributor

Closing, as the linked issue is closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants