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.20:13:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
You've described it correctly.

> The problem is that the warning should be emitted only for users that use incorrect API. But it shouldn't be emitted for users that use just 3.2 API

This is why I suggested #warn and not #error. It's okay to ignore warnings if you know what you're doing, but if there's no warning then people who don't know what they're doing will get it wrong. We know that some people are subtly broken here, and ought to tell them.

Further, if we make the warning only appear for "defined(Py_LIMITED_API) && Py_LIMITED_API+0<0x03000000" then the warning can be suppressed by setting the exact version you intend to use (even though this doesn't prevent you from using the incorrect functions).
Date User Action Args
2016-12-27 20:13:43steve.dowersetrecipients: + steve.dower, vstinner, python-dev, eric.snow, serhiy.storchaka
2016-12-27 20:13:43steve.dowersetmessageid: <>
2016-12-27 20:13:43steve.dowerlinkissue29058 messages
2016-12-27 20:13:42steve.dowercreate