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 loewis, ned.deily, python-dev, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2016-12-26.19:49:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1482781789.43.0.850183062436.issue23903@psf.upfronthosting.co.za>
In-reply-to
Content
Those macros like PyCFunction_New actually need to become functions again, since we need real exports to forward them to the right place. Converting stable API functions to macros breaks the ABI, since modules compiled against the old one can no longer link to newer versions, and modules compiled against newer ones cannot link to older versions.

I'll try and figure out a way we can compile those functions directly into python3.dll, since that's going to leave us with the best ability to use macros for non-stable API builds. We will, however, need to update the header files to define actual functions rather than macros when Py_LIMITED_API is set.
History
Date User Action Args
2016-12-26 19:49:49steve.dowersetrecipients: + steve.dower, loewis, tim.golden, ned.deily, python-dev, zach.ware, serhiy.storchaka
2016-12-26 19:49:49steve.dowersetmessageid: <1482781789.43.0.850183062436.issue23903@psf.upfronthosting.co.za>
2016-12-26 19:49:49steve.dowerlinkissue23903 messages
2016-12-26 19:49:49steve.dowercreate