[issue8350] Document lack of support for keyword arguments in C functions

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue8350] Document lack of support for keyword arguments in C functions

Changes by Yongzhi Pan : -- nosy: +fossilet ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue8350] Document lack of support for keyword arguments in C functions

Mark Lawrence added the comment: Has the Argument Clinic had an impact on this or is that a different kettle of fish? -- nosy: +BreamoreBoy versions: +Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker _

[issue8350] Document lack of support for keyword arguments in C functions

Changes by Ezio Melotti : -- nosy: +ezio.melotti title: Document lack of support for keyword arguments in C functions -> Document lack of support for keyword arguments in C functions versions: +Python 3.3, Python 3.4 -Python 3.1 ___ Python track

[issue8350] Document lack of support for keyword arguments in C functions

Martin v. Löwis 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 s

[issue8350] Document lack of support for keyword arguments in C functions

Terry J. Reedy added the comment: If there is no indication in the lib manual as to which parameter names and defaults are real and which are fake, then the safe guideline is to never use keywards for library functions and methods and always pass everything positionally. Slightly more compli

[issue8350] Document lack of support for keyword arguments in C functions

Terry J. Reedy added the comment: I think that the warning that things are not always as they seem should be repeated in the front of the library manual where the pseudo-arg names are actual used, so the library manual stands on its own. In any case, I believe a lot of people use the lib ref

[issue8350] Document lack of support for keyword arguments in C functions

Raymond Hettinger added the comment: This is an implementation detail specific to CPython and subject to change. I'm -1 on documenting it for every function/method and thereby making it part of the language spec. We've lived without this spec for almost twenty years, so I'm inclined to think

[issue8350] Document lack of support for keyword arguments in C functions

Georg Brandl added the comment: Yes. It's still an important detail; the explanation could say, "In CPython, this function does not take keyword args" and furthermore it's not really clear to me how much of the library reference applies to all Python implementations anyway. --

[issue8350] Document lack of support for keyword arguments in C functions

Antoine Pitrou 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? ---

[issue8350] Document lack of support for keyword arguments in C functions

Georg Brandl 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

[issue8350] Document lack of support for keyword arguments in C functions

Changes by Eric Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8350] Document lack of support for keyword arguments in C functions

Éric Araujo added the comment: You could copy this notice from reference/expressions#calls: “An implementation may provide built-in functions whose positional parameters do not have names, even if they are ‘named’ for the purpose of documentation, and which therefore cannot be supplied by key

[issue8350] Document lack of support for keyword arguments in C functions

Łukasz Langa added the comment: Currently it's somewhat surprising that while the documentation often states the default values for certain builtins, invoking the builtin with keyword arguments as described in the documentation does not work. Original discussion: #7447 I'm going through all

[issue8350] Document lack of support for keyword arguments in C functions

Changes by Éric Araujo : -- title: Explicitly state lack of support for keyword arguments in built-in functions -> Document lack of support for keyword arguments in C functions ___ Python tracker __