This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author aparamon
Recipients andybalaam, aparamon, asvetlov, glin, twisteroid ambassador, yselivanov
Date 2019-02-25.14:55:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> 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
yield await next_fut
Date User Action Args
2019-02-25 14:55:58aparamonsetrecipients: + aparamon, andybalaam, asvetlov, yselivanov, glin, twisteroid ambassador
2019-02-25 14:55:58aparamonsetmessageid: <>
2019-02-25 14:55:58aparamonlinkissue30782 messages
2019-02-25 14:55:58aparamoncreate