Bug report
Bug description:
PEP 739 specifies that the CPython header directory is included in the c_api.headers key. However, it seems that the implemented that landed in #130069 uses c_api.include instead:
{
...
"c_api": {
"include": "/usr/include",
"pkgconfig_path": "/usr/lib64/pkgconfig"
}
}
I don't see any evidence that the name was changed deliberately. In fact, the code seems to be mixing both include and headers names:
|
data['c_api']['include'] = INCLUDEDIR |
|
PATH_KEYS = [ |
|
'base_interpreter', |
|
'libpython.dynamic', |
|
'libpython.dynamic_stableabi', |
|
'libpython.static', |
|
'c_api.headers', |
|
'c_api.pkgconfig_path', |
|
] |
CPython versions tested on:
3.14, CPython main branch
Operating systems tested on:
Linux
Linked PRs
Bug report
Bug description:
PEP 739 specifies that the CPython header directory is included in the
c_api.headerskey. However, it seems that the implemented that landed in #130069 usesc_api.includeinstead:{ ... "c_api": { "include": "/usr/include", "pkgconfig_path": "/usr/lib64/pkgconfig" } }I don't see any evidence that the name was changed deliberately. In fact, the code seems to be mixing both
includeandheadersnames:cpython/Tools/build/generate-build-details.py
Line 126 in 1a07a01
cpython/Tools/build/generate-build-details.py
Lines 138 to 145 in 1a07a01
CPython versions tested on:
3.14, CPython main branch
Operating systems tested on:
Linux
Linked PRs
build-details.jsonto use thec_api.headerskey #134456build-details.jsonto use thec_api.headerskey (GH-134456) #134504