[Python-Dev] Can we make METH_FASTCALL public, from Python 3.7? (ref: PEP 579 (original) (raw)

INADA Naoki songofacandy at gmail.com
Wed Jun 20 13:19:19 EDT 2018

2018年6月21日(木) 1:59 Serhiy Storchaka <storchaka at gmail.com>:

20.06.18 18:42, INADA Naoki пише: > First of all, thank you Jeroen for writing nice PEPs. > > When I read PEP 579, I think "6. METHFASTCALL is private and undocumented" > should be solved first. > > 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. We should to provide also APIs for calling functions using this protocol (PyObjectFastCall) and for parsing arguments (PyArgParseStack). We may want to bikeshed names and the order of arguments for them.

Calling API can be determined later. Even without the API, methods can be called faster from Python core.

But for parsing API, you're right. It should be public with METH_FASTCALL. Only positional arguments can be received without it.

-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180621/0ab9fc0b/attachment.html>

More information about the Python-Dev mailing list