pep-0492: Add a clarification on event loop requirement. By Jim J. Jewett.
This commit is contained in:
parent
19e51828c6
commit
939682f92c
|
@ -27,6 +27,14 @@ is to help establish a common, easily approachable, mental
|
|||
model of asynchronous programming in Python and make it as close to
|
||||
synchronous programming as possible.
|
||||
|
||||
This PEP assumes that the asynchronous tasks are scheduled and
|
||||
coordinated by an Event Loop similar to that of stdlib module
|
||||
``asyncio.events.AbstractEventLoop``. While the PEP is not tied to any
|
||||
specific Event Loop implementation, it is relevant only to the kind of
|
||||
coroutine that uses "yield" as a signal to the scheduler, indicating
|
||||
that the coroutine will be waiting until an event (such as IO) is
|
||||
completed.
|
||||
|
||||
We believe that the changes proposed here will help keep Python
|
||||
relevant and competitive in a quickly growing area of asynchronous
|
||||
programming, as many other languages have adopted, or are planning to
|
||||
|
|
Loading…
Reference in New Issue