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 serhiy.storchaka
Recipients eric.snow, python-dev, serhiy.storchaka, steve.dower, vstinner
Date 2016-12-27.19:59:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Sorry, but perhaps I don't fully understand you.

It is legitimately to just define Py_LIMITED_API without requiring specific version:

    #define Py_LIMITED_API

In that case you can use the stable API of the version 3.2, but can't use PyType_FromSpecWithBases() and PyModule_AddFunctions(), because they are correctly attributed as API of versions 3.3 and 3.5. You can also mistakenly use PyImport_ImportModuleLevelObject() added in 3.5, this is a matter of this issue. But you shouldn't.

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 (perhaps the code was written at the time of 3.2 and was not changed since).
Date User Action Args
2016-12-27 19:59:32serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, python-dev, eric.snow, steve.dower
2016-12-27 19:59:32serhiy.storchakasetmessageid: <>
2016-12-27 19:59:32serhiy.storchakalinkissue29058 messages
2016-12-27 19:59:31serhiy.storchakacreate