-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
gh-134455: Fix build-details.json
to use the c_api.headers
key
#134456
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
…` key Fix `build-details.json` generation to use the correct `c_api.headers` key as defined in PEP 739, instead of `c_api.include`.
CC @FFY00 |
Apparently the standalone tool has the same problem, and someone already submitted a fix for it: FFY00/python-introspection#2 |
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.
Thanks @mgorny!
Yeah, that's the origin of the code I merged into CPython, so it tracks 😅 |
And backport to 3.14? |
Ah, yes, I was forgetting we already branched out. Thanks for the reminder @hugovk! |
…` key (pythonGH-134456) Fix `build-details.json` generation to use the correct `c_api.headers` key as defined in PEP 739, instead of `c_api.include`. (cherry picked from commit d706eb9) Co-authored-by: Michał Górny <mgorny@gentoo.org> Co-authored-by: Filipe Laíns 🇵🇸 <lains@riseup.net>
GH-134504 is a backport of this pull request to the 3.14 branch. |
…` key (python#134456) Fix `build-details.json` generation to use the correct `c_api.headers` key as defined in PEP 739, instead of `c_api.include`. Co-authored-by: Filipe Laíns 🇵🇸 <lains@riseup.net>
Fix
build-details.json
generation to use the correctc_api.headers
key as defined in PEP 739, instead ofc_api.include
.build-details.json
:c_api.include
is used instead ofc_api.headers
#134455