On Thu, Feb 28, 2013 at 11:52 PM, Paul Moore <p.f.mo...@gmail.com> wrote: > On 28 February 2013 13:36, Daniel Holth <dho...@gmail.com> wrote: >> On Thu, Feb 28, 2013 at 4:02 AM, Paul Moore <p.f.mo...@gmail.com> wrote: >>> On 28 February 2013 06:07, Nick Coghlan <ncogh...@gmail.com> wrote: >>>> On Thu, Feb 28, 2013 at 5:47 AM, Paul Moore <p.f.mo...@gmail.com> wrote: >>>>> It's certainly true that the ABI flags are incomplete (there's also >>>>> the whole stable ABI to consider). >>>> >>>> The stable ABI is covered in PEP 425: the stable ABI compatibility tag >>>> is "abi3", and you use the Python version tag to indicate the minimum >>>> required Python version. What part do you feel we missed? >>> >>> You're confusing the tags here. cpXX is the "python" tag, which would >>> be the same for both stable and normal ABI. The ABI tag for the normal >>> ABI is "none". I'd missed the fact that the PEP specifies "abi3" for >>> the stable ABI. >> >> Almost completely right. Technically the ABI for the normal ABI is >> also something like cp33d (d = "with debug"). The scheme is supposed >> to be similar to the filenames inside __pycache__ and of C extensions >> and is backported to Python 2.7. We don't generate these correctly at >> least for Python 2 in the wheel reference. > > OK, we don't generate anything like that for Windows at the moment, > then (where ABI is always "none").
"none" means "this wheel has no dependency on the ABI at all". If a wheel includes C extensions and also has the ABI tag set to none, the tool creating those wheels is broken (although it shouldn't be too harmful in practice if it's also declaring an implementation specific Python dependency, for the reasons already discussed in this thread). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
