Skip to content

Commit 268cc7c

Browse files
andresdelfinoJulienPalard
authored andcommitted
Fix lambda parameters being refered as arguments (GH-7037)
1 parent b7555ba commit 268cc7c

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
@@ -627,7 +627,7 @@ Glossary
627627
lambda
628628
An anonymous inline function consisting of a single :term:`expression`
629629
which is evaluated when the function is called. The syntax to create
630-
a lambda function is ``lambda [arguments]: expression``
630+
a lambda function is ``lambda [parameters]: expression``
631631

632632
LBYL
633633
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
@@ -1608,12 +1608,12 @@ Lambdas
16081608
lambda_expr_nocond: "lambda" [`parameter_list`]: `expression_nocond`
16091609

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

16141614
.. code-block:: none
16151615
1616-
def <lambda>(arguments):
1616+
def <lambda>(parameters):
16171617
return expression
16181618
16191619
See section :ref:`function` for the syntax of parameter lists. Note that

0 commit comments

Comments
 (0)