On Aug 28, 2010, at 12:29 PM, Martin v. Löwis wrote: >The intention is that there is indeed just one stable ABI, so one >configuration is the supported one, and that should be the "default" >build. > >As for the specific settings, my analysis would be this: >- pydebug: not supported by the stable ABI, as it changes the layout > of PyObject, which is an exposed structure > More specifically: Py_DEBUG, Py_TRACEREFS and Py_REF_DEBUG are > all incompatible with the stable ABI >- pymalloc: I fail to see the impact on the ABI. All allocator > macros become function calls under Py_LIMITED_API, otherwise, > there shouldn't be any need to have different versions of that. >- wide-unicode: this is a tricky one. I'm tempted to say that the > stable ABI should always use a Py_UNICODE that matches the platform's > wchar_t. Alternative proposals are welcome.
Thanks Martin. I have updated PEP 3149 with these thoughts, but I'll leave it up to you to update PEP 384. I haven't heard a peep since my last RFC on PEP 3149. Guido, would you care to pronounce on the PEP, or designate someone who can do so (remembering that Martin is off-line for a while)? If acceptable, I'd like to get this into the tree before 3.2 alpha 2, currently scheduled for September 5. Cheers, -Barry
signature.asc
Description: PGP signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
