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 FFY00
Recipients FFY00, dstufft, eric.araujo, jaraco, pablogsal, steve.dower, tarek
Date 2021-08-10.22:25:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
distutils will install the headers to {base}/include/python{py_version_short}{abiflags}/{dist_name}, and I think probably the best option would be to do the same. So, I think we could add a site-include scheme like I described and have the installers append a directory with the distribution name to it.

I think it would be reasonable to put all headers in a shared directory, site-include, given that we make sure the installers put them in a subdirectory for each distribution.

About standardizing pkg-config-like metadata, I don't think that's a great idea, as it would not replace the mechanisms you mentioned. It might replace some, but not all, as there could always be a use-case that needs more information or interaction than what our standard may provide.

Does this make sense to you?
Date User Action Args
2021-08-10 22:25:20FFY00setrecipients: + FFY00, jaraco, tarek, eric.araujo, steve.dower, dstufft, pablogsal
2021-08-10 22:25:20FFY00setmessageid: <>
2021-08-10 22:25:20FFY00linkissue44445 messages
2021-08-10 22:25:20FFY00create