[pypy-dev] Freezing the ".pypy-26.so" name?
Donald Stufft
donald at stufft.io
Sat Jun 13 09:13:35 CEST 2015
On June 13, 2015 at 3:10:39 AM, Armin Rigo (arigo at tunes.org) wrote:
> Hi all,
>
> The cpyext and cffi extension modules are created with the extension
> ".pypy-XY.so", were X and Y are the current PyPy version. I believe
> that there is little point any more: as far as I'm aware, nothing in
> the API changed since a long time, and all these different versions
> are identical to each other. Should we simply freeze the
> ".pypy-26.so" name, so that future PyPy's will also use it, at least
> until some really incompatible change is made?
>
> This would resolve for example issues like
> https://github.com/pypa/pip/issues/2882 .
>
>
> A bientôt,
>
> Armin.
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> https://mail.python.org/mailman/listinfo/pypy-dev
>
For the uses of pip, it would be preferable if there was an exported stable ABI
that we could leverage to tag wheels with. For the people *making* Wheels, the
less often that stable ABI changed the better, since a single wheel would be
useful for more versions of PyPy then.
---
Donald Stufft
PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
More information about the pypy-dev
mailing list