Using a threadpool with asyncio doesn't buy you any parallelism, you have to use a processpool, which is fine for a data processing pipeline. Asyncio does not let you bypass the gil but it does vastly reduce the cost of spinning up absurd amounts of sockets and the like.
It would be nice if someone who groks the async "with" statement could add proper opcode support for it in pycdc. Better to do it when you have spare time than when you've clobbered an important .py file and want to recover it from the .pyc file ASAP. (pycdc can be a life saver.)<p><a href="https://github.com/zrax/pycdc/issues/70" rel="nofollow">https://github.com/zrax/pycdc/issues/70</a>
Isn't this example just like map/reduce in python?<p>I guess it is more like parallel running than async, since I associate async with small sleeping costs and good thread switching. How does the GIL play into this?