If I understand this correctly, the issue is that pip/wheel cannot rely on the ABI version from pypy so they have no way if a wheel would still be compatible or not. So they just generate a different wheel for every version to avoid having to deal with that problem at all. Is that correct? On Tue, Jul 25, 2017 at 1:24 PM Nathaniel Smith <njs@pobox.com> wrote:

On Jul 25, 2017 12:16 PM, "Antonio Cuni" <anto.cuni@gmail.com> wrote:

Hi,

note that this is not because of PyPy: it's the wheel package which chooses what to include in the wheel filename:

https://bitbucket.org/pypa/wheel/src/5d49f8cf18679d1bc6f3e1e414a5df3a1e492644/wheel/pep425tags.py?at=default&fileviewer=file-view-default#pep425tags.py-39

Well, probably it is most correct to say that this happens because PyPy has not come up with a coherent strategy for ABI compatibility and communicated that to wheel/pip :-).

In the mean time, if you want to live dangerously, you can always rename your wheel something like 'foo-py2-pypy_41-linux_x86_64.whl', and then pip will happily install it on newer pypys. Whether it will work though is hard to say...

-n