Comment on Async I/O for Python 3 Comments−pekk13yStill puzzled why the primary inspiration for this is Twisted, which has some really ugly APIs.−timc313ySome people stick with what they know. Twisted is horrible to work with though−zubinmehta13ythat rhymed!−ceronman13yTwisted with inlineCallbacks is actually quite nice IMO. It's very similar to C# async/await.−jlgreco13yTwisted's inlineCallbacks singlehandedly turn Twisted in my mind from an abomination into something that is a joy to work with. In lei of a more hands off Erlang/Go approach, I am convinced that style is the only way to go.−stock_toaster13yinlineCallbacks made twisted palatable. It didn't make it good.−lucian190013yTwisted has excellent APIs. Its Transport and Protocol abstractions in particular are extremely handy.
Comments
Still puzzled why the primary inspiration for this is Twisted, which has some really ugly APIs.
Some people stick with what they know. Twisted is horrible to work with though
that rhymed!
Twisted with inlineCallbacks is actually quite nice IMO. It's very similar to C# async/await.
Twisted's inlineCallbacks singlehandedly turn Twisted in my mind from an abomination into something that is a joy to work with. In lei of a more hands off Erlang/Go approach, I am convinced that style is the only way to go.
inlineCallbacks made twisted palatable. It didn't make it good.
Twisted has excellent APIs. Its Transport and Protocol abstractions in particular are extremely handy.