Antoine Pitrou <pit...@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 <rep...@bugs.python.org> <http://bugs.python.org/issue13785> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
