Author vstinner
Recipients Kevin Mooney, gaige, mcepl, ned.deily, ronaldoussoren, vstinner
Date 2021-09-29.09:36:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1632908213.82.0.0206934139207.issue39026@roundup.psfhosted.org>
In-reply-to
Content
I'm not sure why Include/cpython/ is part of the compiler include directories. I am not sure why Include/ is *not* part of the compiler include directory.

Anyway, it's hard to control how people build Python and there are always legit use cases where you fall into such issue.

That's why I suggest to fix any risk of confusion by renaming Include/cpython/ header files to add a "cpython_" prefix. For example, rename Include/cpython/pystate.h to Include/cpython/cpython_pystate.h.

In the Include/internal/ directory, header files already have a prefix for the exact same reason. For example, there is a pycore_pystate.h file there.
History
Date User Action Args
2021-09-29 09:36:53vstinnersetrecipients: + vstinner, ronaldoussoren, ned.deily, mcepl, gaige, Kevin Mooney
2021-09-29 09:36:53vstinnersetmessageid: <1632908213.82.0.0206934139207.issue39026@roundup.psfhosted.org>
2021-09-29 09:36:53vstinnerlinkissue39026 messages
2021-09-29 09:36:53vstinnercreate