Skip to content

gh-96397: Document that keywords in calls need not be identifiers #96393

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gvanrossum merged 4 commits into from
Sep 22, 2022
Merged

gh-96397: Document that keywords in calls need not be identifiers #96393

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4540b8c
Docs: keywords in calls need not be identifiers
jeff5 Aug 29, 2022
2c0833d
Idiom "whose" in Doc/reference/expressions.rst
jeff5 Aug 29, 2022
d939eb9
Simplify to "instance of str" in Doc/reference/expressions.rst
jeff5 Aug 29, 2022
fd80c3a
"must be a string" instead of a `str` instance
gvanrossum Sep 22, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
"must be a string" instead of a str instance
  • Loading branch information
@gvanrossum
gvanrossum authored Sep 22, 2022
commit fd80c3a2c794a5576a44154580156b7c87514bbb
2 changes: 1 addition & 1 deletion Doc/reference/expressions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1059,7 +1059,7 @@ given a value (by an explicit keyword argument, or from another unpacking),
a :exc:`TypeError` exception is raised.

When ``**expression`` is used, each key in this mapping must be
an instance of :class:`str`.
a string.
Each value from the mapping is assigned to the first formal parameter
eligible for keyword assignment whose name is equal to the key.
A key need not be a Python identifier (e.g. ``"max-temp °F"`` is acceptable,
Expand Down