[issue8350] Document lack of support for keyword arguments in C functions
Georg Brandl <georg@python.org> added the comment: Hmm, it may indeed be the best option to add a new directive option to say "this function does not take keyword args". It would result in some form of unobtrusive but noticeable output in HTML. It is a bit of an effort to add it everywhere it's necessary, but the most important instances (e.g. string methods) can be covered quickly, and it's fairly easy to grep the other instances (namely, grepping for METH_O and METH_VARARGS without METH_KEYWORDS). ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue8350> _______________________________________
Antoine Pitrou <pitrou@free.fr> added the comment:
Hmm, it may indeed be the best option to add a new directive option to say "this function does not take keyword args". It would result in some form of unobtrusive but noticeable output in HTML.
Isn't it kind of a CPython-specific detail, though? ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue8350> _______________________________________
Martin v. Löwis <martin@v.loewis.de> added the comment:
Isn't it kind of a CPython-specific detail, though?
If other implementations do provide proper keyword arguments, I'd be skeptical that they all settled on the names that the library documentation gives to the arguments. ---------- title: Document lack of support for keyword arguments in C functions -> Document lack of support for keyword arguments in C functions _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue8350> _______________________________________
participants (3)
-
Antoine Pitrou -
Georg Brandl
-
Martin v. Löwis