da698e8511
Now that shutdown can be skipped (which would previously wait for all submitted futures to be finished) we need to have a way to know that all submitted futures have been finished before our run method returns. A simple countdown barrier/latch does this so ensure that we use it in the periodic run loop to be able to only return from the run loop when no active futures are in progress. Change-Id: Ia3dd84ebfe2416060aaf5113cc8310a23919a3f9 |
||
---|---|---|
doc/source | ||
futurist | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Futurist
Code from the future, delivered to you in the now. The goal of this library would be to provide a well documented futures classes/utilities/additions that allows for providing a level of transparency in how asynchronous work gets executed. This library currently adds statistics gathering, an eventlet executor, a synchronous executor etc.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/futurist
- Source: http://git.openstack.org/cgit/openstack/futurist
- Bugs: http://bugs.launchpad.net/futurist