On Fri, Nov 9, 2018 at 4:30 PM, Victor Stinner <vstin...@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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
