Typos.
This commit is contained in:
parent
1eee9e2d60
commit
b931f96dea
|
@ -382,7 +382,7 @@ Q & A
|
|||
suggesting such an alternative, and extracted the above from them.
|
||||
It would be nice not to need a new keyword, but nicer to make yield
|
||||
very clear -- I don't want to have to *deduce* that a yield is
|
||||
occurring from making sense of a previous senseless sequence of
|
||||
occurring from making sense of a previously senseless sequence of
|
||||
keywords or operators. Still, if this attracts enough interest,
|
||||
proponents should settle on a single consensus suggestion, and Guido
|
||||
will Pronounce on it.
|
||||
|
@ -396,7 +396,7 @@ Q & A
|
|||
these mechanisms for advanced users. That's not an argument for
|
||||
forcing everyone to work at that level, though. "return" means "I'm
|
||||
done" in any kind of function, and that's easy to explain and to use.
|
||||
Note that "return" isn't always equivalent to "raise StopIteration"
|
||||
Note that "return" isn't always equivalent to "raise StopIteration"
|
||||
in try/except construct, either (see the "Specification: Return"
|
||||
section).
|
||||
|
||||
|
|
Loading…
Reference in New Issue