Skip to content

Commit f808b7a

Browse files
Update lambda.rst: remove the refs since I don't want to hunt them down nor verify them
1 parent 3244b64 commit f808b7a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/guides/lambda.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
The Trouble (Or Lack Thereof) With Lambda
33
*****************************************
44

5-
:ref:`Lambda` expressions are a common and useful part of the Python programming language.
5+
Lambda expressions are a common and useful part of the Python programming language.
66
However, there is one problem with them: syntactically, they do not allow for type
77
annotations. While it is perfectly simple to write ``lambda x: x``, you cannot directly
88
indicate a type for x. (Type annotations are indicated by a colon, and so is the end
@@ -33,12 +33,12 @@ you might as well just define a normal function. Let's call that our first worka
3333
``def f(x: object) -> object: return x``
3434

3535
The second workaround is equivalent: assigning the lambda to a variable, and annotating
36-
the type of that variable with a :ref:`Callable`
36+
the type of that variable with a Callable.
3737

3838
``f: Callable[[object], object] lambda x: x``
3939

40-
:ref:`Type comments on function definitions` do not actually work on lambda, nor do
41-
normal :ref:`Type comments` help (although you can use a type commment on an assignment
40+
Type comments on function definitions do not actually work on lambda, nor do
41+
normal type comments help (although you can use a type commment on an assignment
4242
to a variable with a lambda, of course; however this will have to be the Callable
4343
syntax and not the function-arrow special one).
4444

0 commit comments

Comments
 (0)