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 steve.dower
Recipients FFY00, dstufft, eric.araujo, jaraco, pablogsal, steve.dower, tarek
Date 2021-06-17.16:57:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
distutils.sysconfig doesn't expose the headers path either, it's only there as a default value for the install command (Lib/distutils/command/

So it doesn't seem unreasonable to provide a recommendation on where to put shared header files and let installers do their own calculation. If an installer wants to install into _another_ environment, it can't rely on sysconfig anyway, so we need the spec as well as any implementation. And if we don't have the spec then people will have to reverse-engineer the implementation anyway, so we may as well start with the spec.

Now, whether we actually need or want packages dumping all their headers in one directory is a different question. At least on some platforms they'll also need to import libraries too, and tools like Cython have different files yet again. Many existing project keep these files inside their package and offer the path on request (e.g. pybind11), so perhaps we actually want to standardise pkg-config-like metadata instead?

(Also crossposting back to the discuss thread)
Date User Action Args
2021-06-17 16:57:06steve.dowersetrecipients: + steve.dower, jaraco, tarek, eric.araujo, dstufft, pablogsal, FFY00
2021-06-17 16:57:06steve.dowersetmessageid: <>
2021-06-17 16:57:06steve.dowerlinkissue44445 messages
2021-06-17 16:57:06steve.dowercreate