[Python-Dev] PEP 492 quibble and request (original) (raw)
Ethan Furman ethan at stoneleaf.us
Thu Apr 30 02:21:47 CEST 2015
- Previous message (by thread): [Python-Dev] Unicode literals in Python 2.7
- Next message (by thread): [Python-Dev] PEP 492 quibble and request
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
From the PEP:
Why not a future import
future imports are inconvenient and easy to forget to add.
That is a horrible rationale for not using an import. By that logic we should have everything in built-ins. ;)
Working example ...
The working example only uses async def and await, not async with nor async for nor aenter, etc., etc.
Could you put in a more complete example -- maybe a basic chat room with both server and client -- that demonstrated more of the new possibilities?
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?
--
Ethan
- Previous message (by thread): [Python-Dev] Unicode literals in Python 2.7
- Next message (by thread): [Python-Dev] PEP 492 quibble and request
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]