Javier <jcarm...@gmail.com>:
> I agree with you, Marko, I came from callbacks too. So, if GvR wants
> the yield from become de-facto, does it mean that all python libraries
> will evolve to become asyncio friendly libs? or that I have to write
> my own library so I can use existing libraries like pickle? I think
> "callback hell" is "peccata minuta" compared with "yield from hell".
I guess GvR expects Twisted, Tornado et al jump on the asyncio
bandwagon.
Myself, I would like the lowest-level I/O transactions to be broken into
their atomic, nonblocking primitives:
request optional: update(s), cancellation
response optional: preliminary response(s)
Those primitives can be then used to put together asyncio coroutines or
blocking functions for multithreading. Or they can be used as-is in
classical callback programming.
Marko
--
https://mail.python.org/mailman/listinfo/python-list
