This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Mark.Shannon, kj, vstinner
Date 2022-03-30.14:24:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1648650265.49.0.334418341201.issue47164@roundup.psfhosted.org>
In-reply-to
Content
Hum, there are two things and maybe we are not talking about the same thing.

* (A) Modifying macros defined in the Python C API (Include/ header files) doing cast on their arguments to use CAST macros
* (B) Modify C code doing casts to use CAST macros

I created this issue for (A). I propose to do (B), but this part is optional.

Mark, Ken: are you fine with (A)? Is your concern about (B)?

But modifying macros to remove the cast of their argument is out of the scope of this issue. As I wrote, it would add compiler warnings, something that I would like to avoid. See:
https://peps.python.org/pep-0670/#cast-pointer-arguments
History
Date User Action Args
2022-03-30 14:24:25vstinnersetrecipients: + vstinner, Mark.Shannon, kj
2022-03-30 14:24:25vstinnersetmessageid: <1648650265.49.0.334418341201.issue47164@roundup.psfhosted.org>
2022-03-30 14:24:25vstinnerlinkissue47164 messages
2022-03-30 14:24:25vstinnercreate