Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-28 Thread Paul Moore
On 28 February 2013 00:46, Oscar Benjamin oscar.j.benja...@gmail.com wrote: I apologise if I have misunderstood as I don't understand these things that well. But as someone who uses mingw on Windows (when I am on Windows) I have a question. What if I build with mingw on my computer and then

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-28 Thread Paul Moore
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

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-28 Thread Daniel Holth
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

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-28 Thread Paul Moore
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

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-28 Thread Nick Coghlan
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

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-28 Thread Paul Moore
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

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-28 Thread Vinay Sajip
Paul Moore p.f.moore at gmail.com writes: I'm confused here, because you're mixing up tags. I agree that the ABI tag would have to be different. But cpXY is the *python* tag. Are you saying that extensions for Python compiled with a different MSVCRT should be considered as for a different

[Distutils] The Wheel specification and compatibility tags on Windows

2013-02-27 Thread Vinay Sajip
I have a question about the compatibility tags used by Wheel (PEP 425) and their completeness on Windows. IIUC, it may not be enough to consider the platform and the Python ABI (determined by the Python version). In addition, on Windows, we may have to consider the version of compiler used to

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-27 Thread Daniel Holth
On Wed, Feb 27, 2013 at 12:23 PM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote: I have a question about the compatibility tags used by Wheel (PEP 425) and their completeness on Windows. IIUC, it may not be enough to consider the platform and the Python ABI (determined by the Python version).

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-27 Thread Vinay Sajip
Daniel Holth dholth at gmail.com writes: That is a concern, there seem to be a nearly unlimited number of ways that binaries can be incompatible with your platform, I believe some numpy stuff includes the version of a numeric library in their (non-wheel) system. I designed that assuming

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-27 Thread Chris Lambacher
On Wed, Feb 27, 2013 at 1:01 PM, Vinay Sajip vinay_sa...@yahoo.co.ukwrote: The trouble is, mistakes happen, and people can upload stuff built with the wrong compiler without realising - say, corporates who build their own Pythons, perhaps for embedding scenarios. It may be that in some

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-27 Thread Paul Moore
On 27 February 2013 18:49, Chris Lambacher ch...@kateandchris.net wrote: On Wed, Feb 27, 2013 at 1:01 PM, Vinay Sajip vinay_sa...@yahoo.co.uk wrote: The trouble is, mistakes happen, and people can upload stuff built with the wrong compiler without realising - say, corporates who build their

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-27 Thread Oscar Benjamin
On 27 February 2013 19:47, Paul Moore p.f.mo...@gmail.com wrote: The key on Windows is the version of the MS C runtime. That's what the version of MSVC determines, in essence. Other than MSVC, only gcc (mingw) is supported for building extensions, and gcc builds binaries linking to the same

Re: [Distutils] The Wheel specification and compatibility tags on Windows

2013-02-27 Thread Nick Coghlan
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