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
PyPy reports only the ABI version, which is pypy_41. This is probably wrong for the opposite reasons, i.e. it claims it's backward compatible even when it's not: https://bitbucket.org/pypy/pypy/issues/2613/fix-the-abi-tag ciao, Antonio On Tue, Jul 25, 2017 at 8:47 PM, Daniele Rolando <danieleroland...@gmail.com > wrote: > Hi guys. > > Right now pypy wheels names include both the major and minor pypy version > in them: e.g. uWSGI-2.0.14.0.*pp257*-pypy_41-linux_x86_64.whl > This means that if we want to upgrade pypy from 5.7.1 to 5.8 we'd need to > rebuild all our wheels and this is not scalable since there are new pypy > releases every 3/4 months. > > Wouldn't it be enough to only include the major version in the wheel name? > Are minor pypy versions really incompatible between them? > > Thanks, > Daniele > > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > https://mail.python.org/mailman/listinfo/pypy-dev > >
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev