On Sun, 16 Feb 2020 17:41:36 -0500 Kyle Stanley <[email protected]> wrote: > > As a side note, are we still interested in expanding the public API for the > Future class? Particularly for a public means of accessing the state. The > primary motivation for it was this topic, but I could easily the same > issues coming up with custom Future and Executor classes; not to mention > the general debugging usefulness for being able to log the current state of > the future (without relying on private members).
That sounds useful to me indeed. I assume you mean something like a state() method? We already have Queue.qsize() which works a bit like this (unlocked and advisory). Regards Antoine. _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/7ZQE3IB4NR7ZPLLKWIY54PW3X5K6YWUF/ Code of Conduct: http://python.org/psf/codeofconduct/
