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.

classification
Title: Explicitly state lack of support for keyword arguments in builtin functions
Type: Stage: resolved
Components: Documentation Versions: Python 3.2, Python 2.7
process
Status: closed Resolution: duplicate
Dependencies: Superseder: Document lack of support for keyword arguments in C functions
View: 8350
Assigned To: docs@python Nosy List: docs@python, eric.araujo, eric.smith, lukasz.langa, terry.reedy
Priority: normal Keywords:

Created on 2010-07-30 08:34 by lukasz.langa, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (6)
msg112048 - (view) Author: Łukasz Langa (lukasz.langa) * (Python committer) Date: 2010-07-30 08:34
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 builtins to see how the keyword arg support looks and I'm going to present a patch for Doc/library/builtins.rst that explicitly states that builtins don't support this kind of invocation.

Expect a patch later today.
msg112068 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2010-07-30 11:56
Is this a duplicate of #8350?
msg112072 - (view) Author: Łukasz Langa (lukasz.langa) * (Python committer) Date: 2010-07-30 12:42
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 in #8350 that I believe documentation should include a note that one cannot use specific arguments as keywords.

Both issues cover different parts of documentation so they're not duplicates.
msg112073 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2010-07-30 12:52
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.
msg112074 - (view) Author: Eric V. Smith (eric.smith) * (Python committer) Date: 2010-07-30 13:15
I agree this should be closed and moved to #8350.
msg112077 - (view) Author: Łukasz Langa (lukasz.langa) * (Python committer) Date: 2010-07-30 13:36
Let's do this then :)

Superseded by: #8350
History
Date User Action Args
2022-04-11 14:57:04adminsetgithub: 53672
2010-07-30 13:37:15eric.araujosetresolution: duplicate
superseder: Document lack of support for keyword arguments in C functions
stage: resolved
2010-07-30 13:36:40lukasz.langasetstatus: open -> closed

messages: + msg112077
2010-07-30 13:15:01eric.smithsetnosy: + eric.smith
messages: + msg112074
2010-07-30 12:52:23eric.araujosetmessages: + msg112073
2010-07-30 12:42:40lukasz.langasetmessages: + msg112072
2010-07-30 11:56:43eric.araujosetnosy: + eric.araujo
messages: + msg112068
2010-07-30 08:34:15lukasz.langacreate