Hi Matti,
On Fri, 25 Oct 2019 at 10:21, Matti Picus <matti.pi...@gmail.com> wrote:
>
>
> On 25/10/19 10:49 am, Matti Picus wrote:
> > Yes, actually, thanks. They should be named {python tag}-{abi
> > tag}-{platform tag}, so pypy36-pp72-x86_64-linux-gnu.so. I will make
> > sure the python3.6/python3.7 so names do not overlap before we release
> > a python3.7 alpha.
>
> Needs more thought. The changes in the C-API are reflected in the
> platform tag: 71 is incompatible (perhaps only slightly) with 72. What
> breaking changes are there from the perspective of a C-API module
> between python 3.6 to 3.7, 3.8, 3.9?
The C module itself may contain "#if PY_VERSION_HEX >= 0x03070000" or
similar, in order to compile some feature (or work around some issue)
that is only available on CPython 3.{N} but no 3.{N-1}. So I think
it's a good idea to include both the CPython and the PyPy version in
the name.
A bientôt,
Armin.
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev
