To that end, I propose making asyncio.get_event_loop() a builtin.
I like the idea of making coroutines easier and use. I do too, but ...
Eventloop could have an .__init__ method, or be a factory function, with a 'loop' parameter. The value specifies which eventloop implementation adaptor to use. The default might be 'asyncio', with alternatives such as 'uvloop', 'tkloop' (partly prototyped), 'twisted', and others.
this is a key point -- while asyncio is in the standard library, it is not intended to be THE async event loop implementation -- there are others already, and hopefully that will continue (trio looks pretty cool, for instance...) so yes to making async easier, but no to putting asycio in builtins. even the idea of a builtin EventLoop that other implementations could register with seems kinda pointless -- why not import the one you want? -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov