[Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio (original) (raw)
Jesse Noller jnoller at gmail.com
Sat Sep 28 18:53:47 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 Sep 28, 2013, at 12:59 AM, 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. +1 but up to guido
Cheers, Nick.
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/jnoller%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130928/8977b54b/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 ]