[capi-sig] Re: How can we ship a header file, or even a dynamic library, to port existing C extension modules to the new incompatible Python C API?

Le ven. 5 juin 2020 à 06:19, Hugh Fisher <hugo.fisher@gmail.com> a écrit :

My proposal is that Python.h gets the same treatment as Python 2.7 did, frozen with bug fixes only going forward. After a few years, abandoned.

As far as I recall, Python 2 to Python 3 "flag day" like migration using 2to3 was *not* a success. 2to3 was only looking "forward".

The approach which worked was to use six to have a single code base working on Python 2 and Python 3. I'm trying to do the same. The six approach looks "backward" and it was more successful.

Victor

Night gathers, and now my watch begins. It shall not end until my death.