On Thu, Apr 14, 2016 at 1:22 PM, Matthew Brett <matthew.br...@gmail.com> wrote: > On Thu, Apr 14, 2016 at 8:02 AM, Jens Nielsen <jenshniel...@gmail.com> wrote: >> I have tried testing the wheels in a project that runs tests on Travis's >> Trusty infrastructure which. The wheels work great for python 3.5 and saves >> us several minuts of runtime. >> >> However, I am having trouble using the wheels on python 2.7 on the same >> Trusty machines. It seems to be because the wheels are tagged as cp27-cp27mu >> (numpy-1.11.0-cp27-cp27mu-manylinux1_x86_64.whl) where as >> pip.pep425tags.get_abi_tag() returns cp27m on this particular python >> version. (Stock python 2.7 installed on Travis 14.04 VMs) Any chance of a >> cp27m compatible wheel build? > > Nathaniel / other pip experts - I can't remember the history of these tags. > > Is there any danger that an older pip will install a cp27m wheel on a > cp27mu system?
No, support for cp27m/cp27mu tags went in before support for manylinux tags. And in any case, a pip that doesn't know about cp27m/cp27mu will just not install such wheels. The dangerous case is if you were to use an old version of bdist_wheel that generated a wheel with the "none" abi tag instead of a cp27m/cp27mu abi tag -- this will mess up all versions of pip, new and old. But the manylinux docker image definitely has a new enough version of the wheel package that this is not a problem. ...I guess the other dangerous case is if you generate a wheel that simply has the wrong name -- this happened to the gevent packager due to some distutils brokenness involving using the same source directory to build both wheels. So don't do that :-). (IIRC there's an open bug against auditwheel to check for all these problems -- belt *and* suspenders -- but that hasn't been implemented yet.) -n -- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
