[issue44214] PyArg_Parse* for vectorcall?

Serhiy Storchaka added the comment: There are alternative ideas of parsing API which should be considered: 1. Linearize keyword arguments using _PyArg_UnpackKeywords() and parse the linear array of arguments with a variant of _PyArg_ParseStack(). 2. Parse arguments outside of the user functi

[issue44214] PyArg_Parse* for vectorcall?

Ronald Oussoren added the comment: Annoyingly the keywords variant is the most interesting to expose :-) due to the complexity of correctly interpreting keyword arguments. I agree that we should be careful in exposing the APIs using _PyArg_Parser, although it should be easer to expose it onl

[issue44214] PyArg_Parse* for vectorcall?

Change by Inada Naoki : -- nosy: +methane ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue44214] PyArg_Parse* for vectorcall?

Change by Jeremy Kloth : -- nosy: +jkloth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue44214] PyArg_Parse* for vectorcall?

Serhiy Storchaka added the comment: There are no problems with exposing _PyArg_ParseStack(). Although I am arguing that it would be better to rename it to _PyArg_ParseArray. But _PyArg_ParseStackAndKeywords() is more complicated. It uses a private structure _PyArg_Parser allocated on the sta

[issue44214] PyArg_Parse* for vectorcall?

Change by Ronald Oussoren : -- type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue44214] PyArg_Parse* for vectorcall?

New submission from Ronald Oussoren : I'm currently converting some extensions of my own to vectorcall and an annoying change between the old call protocol and vectorcall is that the latter has no public equivalent to the PyArg_Parse family of functions. There is "_PyArg_ParseStack*" in the C