On 1 November 2013 13:41, Ronald Oussoren <[email protected]> wrote: > > If you build a Wheel with Homebrew Python will it work on the official OSX > installers? What if I have a library installed from Homebrew? Essentially > trying to figure out how likely it is that with the existing tags a wheel is > going to work if we select based on them. > > > Again, someone (and if no-one beats me to it, I) will have to document and > test the various scenarios.
The key point here is the granularity of the PEP 425 tags used by wheel. The risk is that a wheel created on another system might declare (via its filename) that it is compatible with your system, and then not be, causing segfaults or similar when used. On Windows, thanks to the history of bdist_wininst, and the small number of people who build their own *anything* on Windows, there is really only one ABI/C Library/whatever to worry about and that is the python.org one. (Actually, there are two - 32 and 64 bit). If all builds on OSX are compatible at the ABI/CLib/architecture level then there should be no problem. Equally, if incompatible builds result in wheels with different compatibility tags, also no problem. It's only if 2 incompatible environments use the same tags that there could be an issue. I don't believe that linking with external libraries should be a problem here - if wheel X depends on library Y, then either it should include it or it should simply document "Needs library Y installed". It's not a *compatibility* issue as such. But maybe the Unix concept of executables linking to libraries in hard-coded paths might be an issue here, I don't know enough about how that works to say. Hope this clarifies things a bit. Paul _______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
