RetroSearch Browse

Fri Nov 9 20:50:04 EST 2018 · https://mail.python.org/pipermail/python-dev/2018-November/155706.html

On Fri, Nov 9, 2018 at 4:30 PM, Victor Stinner <vstinner at redhat.com> wrote:
> Ah, important points. I don't want to touch the current C API nor make
> it less efficient. And compatibility in both directions (current C API
> <=> new C API) is very important for me. There is no such plan as
> "Python 4" which would break the world and *force* everybody to
> upgrade to the new C API, or stay to Python 3 forever. No. The new C
> API must be an opt-in option, and current C API remains the default
> and not be changed.

Doesn't this mean that you're just making the C API larger and more
complicated, rather than simplifying it? You cite some benefits
(tagged pointers, changing the layout of PyObject, making PyPy's life
easier), but I don't see how you can do any of those things so long as
the current C API remains supported.

-n

-- 
Nathaniel J. Smith -- https://vorpus.org

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2018-November/155706.html below:

[Python-Dev] Experiment an opt-in new C API for Python? (leave current API unchanged)