Minor typo.
This commit is contained in:
parent
42d0692938
commit
b804d61319
|
@ -47,7 +47,7 @@ function object and various attributes on it (including the function's
|
|||
``func_code`` attribute).
|
||||
|
||||
But there is great difficulty when it comes to tuple parameters. The
|
||||
existence of a tuple parameter is denoted by it name being made of a
|
||||
existence of a tuple parameter is denoted by its name being made of a
|
||||
``.`` and a number in the ``co_varnames`` attribute of the function's
|
||||
code object. This allows the tuple argument to be bound to a name
|
||||
that only the bytecode is aware of and cannot be typed in Python
|
||||
|
@ -171,7 +171,7 @@ Practical Use
|
|||
-------------
|
||||
|
||||
In certain instances tuple parameters can be useful. A common example
|
||||
is code that expect a two-item tuple that represents a Cartesian
|
||||
is code that expects a two-item tuple that represents a Cartesian
|
||||
point. While true it is nice to be able to have the unpacking of the
|
||||
x and y coordinates for you, the argument is that this small amount of
|
||||
practical usefulness is heavily outweighed by other issues pertaining
|
||||
|
|
Loading…
Reference in New Issue