[Python-Dev] PEP 492 quibble and request (original) (raw)
Paul Moore p.f.moore at gmail.com
Thu Apr 30 11:07:15 CEST 2015
- Previous message (by thread): [Python-Dev] PEP 492 quibble and request
- Next message (by thread): [Python-Dev] Clarification of PEP 476 "opting out" section
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 30 April 2015 at 09:58, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
Ethan Furman wrote:
Having gone through the PEP again, I am still no closer to understanding what happens here: data = await reader.read(8192) What does the flow of control look like at the interpreter level? Are you sure you really want to know? For the sake of sanity, I recommend ignoring the actual control flow and pretending that it's just like data = reader.read(8192) with the reader.read() method somehow able to be magically suspended.
Well, if I don't know, I get confused as to where I invoke the event loop, how my non-async code runs alongside this etc. Paul
- Previous message (by thread): [Python-Dev] PEP 492 quibble and request
- Next message (by thread): [Python-Dev] Clarification of PEP 476 "opting out" section
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]