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 andrewtomazos
Recipients andrewtomazos, eric.smith, jpelizza
Date 2021-02-26.08:46:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
After studying the include directives in the Include folder, I think the best fix would be:

In Include/cpython/state.h:

    - #include "cpython/initconfig.h"
    + #include "initconfig.h"

this will mean that state.h will find initconfig.h using a file-relative include (as all the other include directives do), instead of relying on the installed Include directory being put in the header search path.

As this include directive is the only one with this property, the benefit of this change would be that the Include folder would be able to be installed in any subdirectory of a search path, rather than requiring its own dedicated one.

This would mean (for example) you could install different versions of the Python headers side by side and then select between them using preprocessor directives - rather than having to switch up global compiler options.
History
Date User Action Args
2021-02-26 08:46:27andrewtomazossetrecipients: + andrewtomazos, eric.smith, jpelizza
2021-02-26 08:46:27andrewtomazossetmessageid: <[email protected]>
2021-02-26 08:46:27andrewtomazoslinkissue40642 messages
2021-02-26 08:46:27andrewtomazoscreate