[issue9426] Explicitly state lack of support for keyword arguments in builtin functions

Changes by Éric Araujo : -- resolution: -> duplicate stage: -> committed/rejected superseder: -> os.mkdir doc comment is incorrect ___ Python tracker ___ __

[issue9426] Explicitly state lack of support for keyword arguments in builtin functions

Łukasz Langa added the comment: Let's do this then :) Superseded by: #8350 -- status: open -> closed ___ Python tracker ___ ___ Pytho

[issue9426] Explicitly state lack of support for keyword arguments in builtin functions

Eric Smith added the comment: I agree this should be closed and moved to #8350. -- nosy: +eric.smith ___ Python tracker ___ ___ Python

[issue9426] Explicitly state lack of support for keyword arguments in builtin functions

Éric Araujo added the comment: The title of #8350 is outdated. The discussion has shifted from one specific function to the general doc problem. Since it contains references and opinions, I think it supersedes this one. -- ___ Python tracker

[issue9426] Explicitly state lack of support for keyword arguments in builtin functions

Łukasz Langa added the comment: Same problem, different context. Here we have an already accepted idea (from #7447) to extend the documentation by providing an explicit explanation that named arguments in builtins are usually positional only, contrary to the intuition. I've already commented

[issue9426] Explicitly state lack of support for keyword arguments in builtin functions

Éric Araujo added the comment: Is this a duplicate of #8350? -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9426] Explicitly state lack of support for keyword arguments in builtin functions

New submission from Łukasz Langa : 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 al