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 steve.dower
Recipients eric.snow, python-dev, serhiy.storchaka, steve.dower, vstinner
Date 2016-12-27.19:32:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Just defining Py_LIMITED_API actually implies =0x03020000.

That's the intent, but if it were actually the case then this issue wouldn't exist :)

On 3.5.3, building with Py_LIMITED_API=1 will include APIs that should only be included when Py_LIMITED_API=0x03050000. You considered fixing that too likely to break existing users (and I agree), but that doesn't mean we shouldn't make it clear that it's not doing exactly the right thing.

> I have no idea where a #warn can be added.

pyport.h or pymacro.h are probably the best places. If you null-merge into 3.6 then we shouldn't have to worry about the warning showing up in later versions.
Date User Action Args
2016-12-27 19:32:07steve.dowersetrecipients: + steve.dower, vstinner, python-dev, eric.snow, serhiy.storchaka
2016-12-27 19:32:07steve.dowersetmessageid: <>
2016-12-27 19:32:07steve.dowerlinkissue29058 messages
2016-12-27 19:32:07steve.dowercreate