Skip to content

Commit d9055f8

Browse files
Fix lambda parameters being refered as arguments (GH-7037)
(cherry picked from commit 268cc7c) Co-authored-by: Andrés Delfino <adelfino@gmail.com>
1 parent 2b4ed5d commit d9055f8

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

Doc/glossary.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -603,7 +603,7 @@ Glossary
603603
lambda
604604
An anonymous inline function consisting of a single :term:`expression`
605605
which is evaluated when the function is called. The syntax to create
606-
a lambda function is ``lambda [arguments]: expression``
606+
a lambda function is ``lambda [parameters]: expression``
607607

608608
LBYL
609609
Look before you leap. This coding style explicitly tests for

Doc/reference/expressions.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1613,12 +1613,12 @@ Lambdas
16131613
lambda_expr_nocond: "lambda" [`parameter_list`]: `expression_nocond`
16141614

16151615
Lambda expressions (sometimes called lambda forms) are used to create anonymous
1616-
functions. The expression ``lambda arguments: expression`` yields a function
1616+
functions. The expression ``lambda parameters: expression`` yields a function
16171617
object. The unnamed object behaves like a function object defined with:
16181618

16191619
.. code-block:: none
16201620
1621-
def <lambda>(arguments):
1621+
def <lambda>(parameters):
16221622
return expression
16231623
16241624
See section :ref:`function` for the syntax of parameter lists. Note that

0 commit comments

Comments
 (0)