On Wed, Jan 13, 2010 at 2:01 AM, David Cournapeau <[email protected]> wrote: > On Wed, Jan 13, 2010 at 3:08 AM, Nate Coraor <[email protected]> wrote: > >> >> It's not even crucial to me that these be fixed, but before I continue to >> hack up the platform string, I wanted to ask the SIG to address these issues >> and hopefully decide on a standard. That way, I can at least implement >> patches in my app that will be compatible with whatever (if anything) is >> decided. > > I think the only reasonable approach today is to admit that python > does not have a well defined ABI (but see PEP 384), and only target > well known binary distributions. On mac os x, only target the python > from python.org, etc... > > IMHO, all the attempts at distinguishing between UCS2 vs UCS4, etc... > are flawed, because that's only the tip of the iceberg, and it quickly > gives a big number of combinations. Cramming information into > get_platform to pretend it gives some kind of ABI guarantee does not > sound very robust.
Besides a well-defined ABI, if usc2/usc4 + 32/64 bits distinction on some platforms already fixes a numbers of use cases, I think could worth it for 2.7/3.2 _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
