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

fixed a couple of typos

This commit is contained in:
Just van Rossum 2005-01-14 19:01:09 +00:00
parent 95bf581983
commit c38198cfef
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0246.txt
View File

@ -325,12 +325,12 @@ Guido's "Optional Static Typing: Stop the Flames" Blog Entry
def f(X):
X = adapt(X, Y)
# continue by using X according to protocol X
# continue by using X according to protocol Y
In [4], the BDFL has proposed introducing the syntax:
def f(X: Y):
# continue by using X according to protocol X
# continue by using X according to protocol Y
to be a handy shortcut for exactly this typical use of adapt, and,
as a basis for experimentation until the parser has been modified
@ -338,7 +338,7 @@ Guido's "Optional Static Typing: Stop the Flames" Blog Entry
@arguments(Y)
def f(X):
# continue by using X according to protocol X
# continue by using X according to protocol Y
These BDFL ideas are fully compatible with this proposal, as are
other of Guido's suggestions in the same blog.
@ -615,7 +615,7 @@ Questions and Answers
appropriate adapter, but even then searching for the adapter
and figuring out how to deploy the adapter takes time.
This technique enables supplierrs to work with each other
This technique enables suppliers to work with each other
directly, by implementing __conform__ or __adapt__ as
necessary. This frees the integrator from making their own
adapters. In essence, this allows the components to have a