Message336526
> an implicit requirement that back pressure from the consumer should be handled (i.e. if whoever's iterating through "async for fut in as_completed(...)" is too slow, then the tasks should pause until it catches up)
No, I don't think it is required or desired to be handled.
My initial sketch was imprecise: it's better to asynchronously yield task results, not "completed task" futures. This way, no additional buffer needed, all error handling can be consolidated inside `igather()`, and that's actually more compatible with `asyncio.gather()`.
I.e, instead of
----
yield next_fut
----
use
----
yield await next_fut
---- |
|
Date |
User |
Action |
Args |
2019-02-25 14:55:58 | aparamon | set | recipients:
+ aparamon, andybalaam, asvetlov, yselivanov, glin, twisteroid ambassador |
2019-02-25 14:55:58 | aparamon | set | messageid: <1551106558.64.0.83048434945.issue30782@roundup.psfhosted.org> |
2019-02-25 14:55:58 | aparamon | link | issue30782 messages |
2019-02-25 14:55:58 | aparamon | create | |
|