[Python-Dev] PEP 492: Please mention the Event Loop (original) (raw)
Paul Moore p.f.moore at gmail.com
Tue May 5 23:31:56 CEST 2015
- Previous message (by thread): [Python-Dev] PEP 492: Please mention the Event Loop
- Next message (by thread): [Python-Dev] PEP 492: Please mention the Event Loop
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5 May 2015 at 22:09, Jim J. Jewett <jimjjewett at gmail.com> wrote:
Proposed second paragraph of the abstract:
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.
+1. If that's not accurate then by all means correct any mistakes in it. But assuming it is accurate, it would help a lot. Paul
- Previous message (by thread): [Python-Dev] PEP 492: Please mention the Event Loop
- Next message (by thread): [Python-Dev] PEP 492: Please mention the Event Loop
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]