Feb. 17, 2020
12:39 p.m.
On Mon, 17 Feb 2020 12:19:59 -0800 Guido van Rossum <guido@python.org> wrote:
It's actually really hard to implement your own Future class that works well with concurrent.futures.as_completed() -- this is basically what complicated the OP's implementation. Maybe it would be useful to look into a protocol to allow alternative Future implementations to hook into that?
Ah, I understand the reasons then. Ok, it does sound useful to explore the space of solutions. But let's decouple it from simply querying the current Future state. Regards Antoine.