RetroSearch Browse

Fri Nov 9 19:56:02 EST 2018 · https://mail.python.org/pipermail/python-dev/2018-November/155705.html

Le sam. 10 nov. 2018 à 01:49, Michael Selik <mike at selik.org> a écrit :
>> It uses an opt-in option (Py_NEWCAPI define -- I'm not sure about the
>> name) to get the new API. The current C API is unchanged.
>
> While one can hope that this will be the only time the C API will be revised, it may be better to number it instead of calling it "NEW". 20 years from now, it won't feel new anymore.

That's exactly why I dislike "New", it's like adding "Ex" or "2" to a
function name :-)

Well, before bikeshedding on the C define name, I would prefer to see
if the overall idea of trying to push code for the new C API in the
master branch is a good idea, or if it's too early and the experiment
must continue in a fork.

Victor

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

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

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