[New-bugs-announce] [issue13785] Make concurrent.futures.Future state public
Juan Javier
report at bugs.python.org
Sat Jan 14 18:07:15 CET 2012
New submission from Juan Javier <jjdominguezm at gmail.com>:
Hello,
This is a proposal to make the state of Future objects public.
The idea is to have access to the current state of the Future using a property instead of calling several methods (done, cancelled, etc.).
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.
There is a patch attached to the issue.
Regards.
----------
components: Library (Lib)
files: concurrent.futures.Future.state_public.patch
keywords: patch
messages: 151259
nosy: bquinlan, jjdominguezm
priority: normal
severity: normal
status: open
title: Make concurrent.futures.Future state public
type: enhancement
versions: Python 3.3
Added file: http://bugs.python.org/file24237/concurrent.futures.Future.state_public.patch
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13785>
_______________________________________
More information about the New-bugs-announce
mailing list