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

pep-0492: Update Rationale section

This commit is contained in:
Yury Selivanov 2015-05-04 19:35:36 -04:00
parent ff91b78ea3
commit 9d82c29bd8
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
pep-0492.txt
View File

@ -38,15 +38,15 @@ Current Python supports implementing coroutines via generators (PEP
342), further enhanced by the ``yield from`` syntax introduced in PEP 342), further enhanced by the ``yield from`` syntax introduced in PEP
380. This approach has a number of shortcomings: 380. This approach has a number of shortcomings:
* it is easy to confuse coroutines with regular generators, since they * It is easy to confuse coroutines with regular generators, since they
share the same syntax; async libraries often attempt to alleviate share the same syntax; this is especially true for new developers.
this by using decorators (e.g. ``@asyncio.coroutine`` [1]_);
* it is not possible to natively define a coroutine which has no * Whether or not a function is a coroutine is determined by a presence
``yield`` or ``yield from`` statements, again requiring the use of of ``yield`` or ``yield from`` statements in its *body*, which can
decorators to fix potential refactoring issues; lead to unobvious errors when such statements appear in or disappear
from function body during refactoring.
* support for asynchronous calls is limited to expressions where * Support for asynchronous calls is limited to expressions where
``yield`` is allowed syntactically, limiting the usefulness of ``yield`` is allowed syntactically, limiting the usefulness of
syntactic features, such as ``with`` and ``for`` statements. syntactic features, such as ``with`` and ``for`` statements.