This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients jkloth, methane, ronaldoussoren, serhiy.storchaka
Date 2021-05-25.14:39:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1621953597.9.0.866979991758.issue44214@roundup.psfhosted.org>
In-reply-to
Content
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 only in the non-stable ABI because extensions should be recompiled for new python releases anyway.

That said, I won't work on this issue myself (or at least not anytime soon). My current use case doesn't use keyword arguments, and open coding the calls to PyArg_ParseTuple is easy enough for now (even if that leads to more boilerplate).
History
Date User Action Args
2021-05-25 14:39:57ronaldoussorensetrecipients: + ronaldoussoren, jkloth, methane, serhiy.storchaka
2021-05-25 14:39:57ronaldoussorensetmessageid: <1621953597.9.0.866979991758.issue44214@roundup.psfhosted.org>
2021-05-25 14:39:57ronaldoussorenlinkissue44214 messages
2021-05-25 14:39:57ronaldoussorencreate