[Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Sat Sep 28 12:55:21 CEST 2013
- Previous message: [Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio
- Next message: [Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, 28 Sep 2013 15:59:05 +1000 Nick Coghlan <ncoghlan at gmail.com> wrote:
It sounds like a reasonable approach to me.
In terms of naming, would you consider "concurrent.asyncio"? When we created that parent namespace for futures, one of the other suggested submodules discussed was the standard event loop API.
-10. Please, let's stop it.
Regards
Antoine.
- Previous message: [Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio
- Next message: [Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]