On 27 November 2017 at 18:41, Nathaniel Smith wrote:
>
> In asyncio, the convention is that the values you send back must be
> Future objects,
Thanks this is useful. I didn't pick this up from the various PEPs or
documentation. I guess I need to go through the src :)
___
On 27 November 2017 at 14:53, Yury Selivanov
wrote:
> It is correct. While 'yield from coro()', where 'coro()' is an 'async
> def' coroutine would make sense in some contexts, it would require
> coroutines to implement the iteration protocol. That would mean that
> you could write 'for x in cor
On 27 November 2017 at 13:20, David Mertz wrote:
>
> Imagining that 'yield' vanished from the language tomorrow, and I wanted
> to write the same thing with async/await, I think the best I can come up
> with is... actually, I just don't know who to do it without any `yield`.
>
I recently had to l
