Skip to content

Commit ab90ea2

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 0c1e7d8 commit ab90ea2

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

Doc/glossary.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -595,7 +595,7 @@ Glossary
595595
lambda
596596
An anonymous inline function consisting of a single :term:`expression`
597597
which is evaluated when the function is called. The syntax to create
598-
a lambda function is ``lambda [arguments]: expression``
598+
a lambda function is ``lambda [parameters]: expression``
599599

600600
LBYL
601601
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
@@ -1571,12 +1571,12 @@ Lambdas
15711571
lambda_expr_nocond: "lambda" [`parameter_list`]: `expression_nocond`
15721572

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

15771577
.. code-block:: none
15781578
1579-
def <lambda>(arguments):
1579+
def <lambda>(parameters):
15801580
return expression
15811581
15821582
See section :ref:`function` for the syntax of parameter lists. Note that

0 commit comments

Comments
 (0)