[Python-Dev] Can we make METH_FASTCALL public, from Python 3.7? (ref: PEP 579 (original) (raw)
Stefan Behnel stefan_ml at behnel.de
Wed Jun 20 13:45:16 EDT 2018
- Previous message (by thread): [Python-Dev] Can we make METH_FASTCALL public, from Python 3.7? (ref: PEP 579
- Next message (by thread): [Python-Dev] Can we make METH_FASTCALL public, from Python 3.7? (ref: PEP 579
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Serhiy Storchaka schrieb am 20.06.2018 um 18:56:
20.06.18 18:42, INADA Naoki пише:
I don't have any idea about changing METHFASTCALL more. If Victor and Serhiy think so, and PyPy maintainers like it too, I want to make it public as soon as possible. I don't have objections against making the METHFASTCALL method calling convention public. But only for positional-only parameters, the protocol for keyword parameters is more complex and still can be changed.
That's also the level that Cython currently uses/supports, exactly because keyword arguments are a) quite a bit more complex, b) a lot less often used and c) pretty much never used in performance critical code.
Cython also currently limits the usage to Py3.6+, although I'm considering to generally enable it for everything since Py2.6 as soon as Cython starts using the calling convention for its own functions, just in case it ends up calling itself without prior notice. :)
Stefan
- Previous message (by thread): [Python-Dev] Can we make METH_FASTCALL public, from Python 3.7? (ref: PEP 579
- Next message (by thread): [Python-Dev] Can we make METH_FASTCALL public, from Python 3.7? (ref: PEP 579
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]