On Mon, 17 Feb 2020 12:19:59 -0800 Guido van Rossum <gu...@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. _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/5UJSZP47TA3ULWNFAG33NFL4KL75QC2Y/ Code of Conduct: http://python.org/psf/codeofconduct/
