because I use homebrew,I am converted to an OS X developer since 2006, but never had ABI problems,
but instead of being set free on Windows after 30 years
of pain, I now have the same mess in my Parallels VMs.
Customers are so cruel, aren't they?
Would be great, but I would not mind to create their extensions on stackless.com, instead.Do you want people to be able to use extensions built by third parties for python.org CPython with your binary builds?
Yes, I want to make PIP work with it, want to make it very simple to installThe other potential route for error is a pip install -- you don't want pip to find a binary that is incompatible with your build -- so you should assure that whatever pip/wheel uses to identify the build is set differently in your build (see the relevant PEPs).
whatnot, and let people use that stuff. So if you can, please teach me
what I need to do or avoid.
What I want is a workable CPython path for some customer (!=CCP) to use
for the next (maybe 5) years, and I want to build that now, for good.
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.