Yury Selivanov
Yury Selivanov
It's not even a `yield from` bug: ``` python class MainError(Exception): pass class SubError(Exception): pass def main(): try: raise MainError() except MainError: try: yield except SubError: print('got SubError') raise coro...
http://bugs.python.org/issue25612
Do you want to fix this before 3.6 b2?
> To be honest, the most untuitive one was asyncio.async, but got deprecated for some reason. I like asyncio.async() much more than either asyncio.ensure_future() or asyncio.create_task(). The reason is “async”...
`ensure_future` can accept `Future`s and `Task`s, in addition to coroutines. If it's the latter, it will wrap it in a `Task`. If it's the former, it will just return the...
> Maybe there should be an alias for that asyncio.create_task()? Yes, that's the idea. It would be nice to have a way to create tasks without explicit loop handling. So...
> OK, I'm not totally against spawn() then. I think we should have a PEP describing all the (major) improvements we want to make to asyncio in Python 3.7 rather...
> It would be hugely backward compatible. It would also be a huge bug magnet > -- diagnostics if you forget to await the close() call are minimal. @gvanrossum sorry,...