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 martin.panter
Recipients benjamin.peterson, lukasz.langa, martin.panter, ned.deily, steven.daprano
Date 2016-09-12.05:38:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473658685.1.0.741458809004.issue28092@psf.upfronthosting.co.za>
In-reply-to
Content
Benjamin changed PEP 7 to allow static inline functions directly in Python 3.6. But later he added program-wide, linkable inline functions in the Python 3.6 code:

2f77a9f0b9d6: add plain “inline” to header file
63ae310b60ff: add “extern inline” stubs in a new file

It seems GCC does not support the C99 syntax for these kind of linkable inline functions until 4.3. Some possible fixes or workarounds:

1. Revert the offending functions back to macros

2. Clarify in PEP 7 that we intentionally use linkable C99 (extern) inline functions, therefore compilers like Steven’s and the buildbot’s aren’t supported for 3.6

3. Add some preprocessor magic based on __GNUC_STDC_INLINE__ to detect when the GCC 4.0 reversed meanings of “inline” and “extern inline” have to be used.
History
Date User Action Args
2016-09-12 05:38:05martin.pantersetrecipients: + martin.panter, benjamin.peterson, ned.deily, steven.daprano, lukasz.langa
2016-09-12 05:38:05martin.pantersetmessageid: <1473658685.1.0.741458809004.issue28092@psf.upfronthosting.co.za>
2016-09-12 05:38:05martin.panterlinkissue28092 messages
2016-09-12 05:38:04martin.pantercreate