➜

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 petr.viktorin
Recipients Arfrever, FFY00, brett.cannon, christian.heimes, doko, dstufft, eric.araujo, frenzy, hugovk, ionelmc, jaraco, lukasz.langa, methane, ncoghlan, ned.deily, p-ganssle, pablogsal, paul.moore, petr.viktorin, steve.dower, xtreak
Date 2021-05-24.12:13:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1621858388.49.0.0511863610639.issue41282@roundup.psfhosted.org>
In-reply-to
Content 
When building Python, we need two distinct "include" directories:
- source .h files
- install target for .h files

Note that this doesn't matter except when building Python from source.

Historically:
- source .h files were in the sysconfig scheme under 'include'
- the install directory was in the distutils.command.install scheme
    under 'headers'

GH-24549 merged these, because sysconfig is now the single source of truth and distutils is derived from it.
It seems to me that we need to bring 'headers' back -- at least when building Python.
History
Date User Action Args
2021-05-24 12:13:08petr.viktorinsetrecipients: + petr.viktorin, brett.cannon, doko, paul.moore, jaraco, ncoghlan, christian.heimes, ned.deily, eric.araujo, Arfrever, ionelmc, methane, lukasz.langa, steve.dower, dstufft, p-ganssle, frenzy, pablogsal, hugovk, xtreak, FFY00
2021-05-24 12:13:08petr.viktorinsetmessageid: <1621858388.49.0.0511863610639.issue41282@roundup.psfhosted.org>
2021-05-24 12:13:08petr.viktorinlinkissue41282 messages
2021-05-24 12:13:08petr.viktorincreate