[Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Sat Sep 28 07:59:05 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 ]
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.
Cheers, Nick. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130928/aa4ee948/attachment.html>
- 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 ]