ee42ab588a
SystemExit exception is usually raised by signal handlers and then caught in main thread to handle signal. Signal handler executes in main threads but if we use eventlet we have ony one thread and signal handler can interrupt any greenlet. Therefore we need to re-raise this exception to catch it in main greenlet at last. Also it is necessary to keep executor working and continue processing scheduled tasks because signal handling logic may wait for some job results Change-Id: Ia920922d8444c8216b442577c37710538ed8e919 |
||
---|---|---|
doc/source | ||
futurist | ||
releasenotes | ||
tools | ||
.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
Team and repository tags
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