On 31 October 2013 23:38, Ronald Oussoren <ronaldoussoren@mac.com> wrote:
On 21 Oct, 2013, at 20:52, Donald Stufft <donald@stufft.io> wrote:
On Oct 21, 2013, at 1:02 PM, Chris Barker <chris.barker@noaa.gov> wrote:
On Fri, Oct 18, 2013 at 6:22 PM, Nick Coghlan <ncoghlan@gmail.com> wrote:
-- it would be very useful if folks could easily get binary wheels for OS-X
We do plan to support it, but the pip devs uncovered a hole in the current wheel spec that means it generates the same filename on *nix systems for wheels that need to have different names for the download side of things to work properly
THanks -- but really? don't OS-X wheels get:
macosx_10_6_intel
or some such tacked on? Where does that go wrong?
Homebrew, Mac Ports, Fink. That would work OK if nobody ever installed things that the system didn't provide.
I don't understand this, what would break? Binary wheels that reference shared libraries that aren't included in the wheel (or a default system install) won't work, but that's also true on Windows.
The main difference I see is that on Windows, the ABI for the *CPython* shared library is significantly less likely to vary across machines. By contrast, it's relatively easy to change the ABI on *nix systems, as it depends on what you pass as configure options. Will a C extension built with Homebrew Python work with the Python Mac OS X installer from python.org? Probably, but given how painful ABI mismatches with shared libraries can be to debug, "probably" doesn't cut it until someone has the chance to thoroughly review the potential for problems. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia