On Thu, Nov 21, 2013 at 4:12 PM, Paul Moore <p.f.mo...@gmail.com> wrote: > On 21 November 2013 21:02, Greg Ewing <greg.ew...@canterbury.ac.nz> wrote: >> Is that much different from package authors having to >> release binaries for different versions of Python, >> if they want to support older versions? >> >> Having multiple binaries for the same x.y version >> is different from what's been done before, but it >> seems to me an unavoidable consequence of supporting >> one x.y version for longer than usual. > > None of the currently available binary distribution formats > distinguish Windows binaries by anything other than minor version. For > wheels (and I think eggs), this is a showstopper as the name is > essential metadata (compatibility tags) for the other formats (wininst > and msi) the name is merely informational - packagers could rename, > but (a) they will forget, and (b) the users won't know if they have or > not. > > Before we can cleanly support multiple ABIs for a single minor version > on Windows, we need to have a resolution of this dilemma (which may be > nothing more than "only binaries for the python.org builds are allowed > on PyPI"...) > > Paul
As for wheel it actually does support an ABI tag that is separate from the Python version and the architecture. It's the second one pyversion-abi-architecture as in py27-none-any or py27-cp27-linux_i386 (spelling?). The build tool and installer would have to be modified to be aware of any newly defined ABI tags. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com