iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix typos

This commit is contained in:
George Yoshida 2007-05-18 01:30:16 +00:00
parent f8c26057aa
commit de0c02d370
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pep-3113.txt
View File

@ -87,7 +87,7 @@ No Loss of Abilities If Removed
As mentioned in `Introspection Issues`_, to handle tuple parameters
the function's bytecode starts with the bytecode required to unpack
the argument into the proper parameter names. This means that their
the argument into the proper parameter names. This means that there
is no special support required to implement tuple parameters and thus
there is no loss of abilities if they were to be removed, only a
possible convenience (which is addressed in
@ -170,7 +170,7 @@ Practical Use
-------------
In certain instances tuple parameters can be useful. A common example
is code that expect a two-item tuple that reperesents a Cartesian
is code that expect 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