[issue13785] Make concurrent.futures.Future state public

Antoine Pitrou report at bugs.python.org
Mon Jan 16 00:04:50 CET 2012

Antoine Pitrou <pitrou at free.fr> added the comment:

> The idea is to have access to the current state of the Future using a property instead of calling several methods (done, cancelled, etc.).

I think one point of having methods is that querying is decoupled from implementation. The internal states could for example be finer-grained than what is exposed by the API.

> Also, a history property that returns a list of Event(state, timestamp) objects is written, the list stores the timestamp every time the state of a future changes.

Uh, what is the use case exactly?

nosy: +pitrou

Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list