IssueRaiser

I 'll add my experience with asyncio and twisted: 1) debugging is way better in asyncio, with ipdb you can step in co-routine.

I 'll add my experience with asyncio and twisted: 1) debugging is way better in asyncio, with ipdb you can step in co-routine. In twisted, you will end up somewhere in internals. 2) asyncio is end of unhanded error in deferred :) (or you need to remember to add addErrback everywhere, even after addColbecks and addBoth) 3) with trial testing is frustrating, sometimes error raised in wrong test because of global event loop (for instance you forgot to mock external call). In asyncio world loop passed explicitly and this is good for testing.

Posted by phenom on Apr 21, 2015, 8:41 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.7,000 issues0 comments

hackernews (Other)

I 'll add my experience with asyncio and twisted: 1) debugging is way better in asyncio, with ipdb you can step in co-routine.

phenomApr 21, 2015, 8:41 PM

I 'll add my experience with asyncio and twisted: 1) debugging is way better in asyncio, with ipdb you can step in co-routine. In twisted, you will end up somewhere in internals. 2) asyncio is end of unhanded error in deferred :) (or you need to remember to add addErrback everywhere, even after addColbecks and addBoth) 3) with trial testing is frustrating, sometimes error raised in wrong test because of global event loop (for instance you forgot to mock external call). In asyncio world loop passed explicitly and this is good for testing.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue