[python-tulip] GC raise of GeneratorExit and naked except clauses

I have an experimental library where I manage the lifecycle of event loops for purposes of allowing async routines to operate inside a classical generator (among other things). I create a new event loop for each use of my routine and upon completion or GC this event loop is closed. My recent

Re: [python-tulip] Motor, the async MongoDB driver, now supports asyncio

Awesome, Jesse, Andrew, Nikolay and all, congratulations! I just tweeted the good news to 3239 followers: https://twitter.com/ramalhoorg/status/672751521453506560 Cheers, Luciano On Wed, Dec 2, 2015 at 12:33 AM, A. Jesse Jiryu Davis wrote: > Hi friends — with help

Re: [python-tulip] Asynchronous console and interfaces

> At the end, you got the idea. > It is readable, portable, generic, etc, etc.. > "This" should be underlined in asyncio documentation. > Not the protocols, callbacks, futures, transports... I think they're all very different objects: - callbacks, futures and coroutines are the core of asyncio;

Re: [python-tulip] GC raise of GeneratorExit and naked except clauses

Hi Justin, I think in the long run the event loop (and everything in asyncio) needs to be much more careful with BaseExceptions. Their treatment is uneven -- if we're writing "except Exception" they are not caught, but when we're writing "finally" or "except: ...; raise" they are caught. I think