
On 21 November 2013 21:31, <martin@v.loewis.de> wrote:
Quoting Nick Coghlan <ncoghlan@gmail.com>:
Another alternative I'd prefer to an ABI version bump: backporting the "C runtime independence" aspects of the stable ABI to Python 2.7.
P.S. Thinking about this, there are some issues. The "restricted API" hides the object layout of all objects, in particular of type objects. Adding the PEP 384 API (PyType_FromSpec) might be a bit heavy for 2.7.
So it might by better to provide a "py27compat.dll" instead which does not hide the structures (as they won't change during the remaining life of 2.7), but only hides any APIs and macros that directly expose CRT functionality.
Yep, that's what I meant by backporting just the "C runtime independence" aspects - there's no reason to backport the version independence features, since we're not planning to do another Python 2.x ABI bump anyway. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia