Go to file
Joshua Harlow 1478f52c9a Retain nested causes where/when we can
On py3.x we should attempt to retain an exceptions
causes (if any) so that they can be examined at a later
time. This adds that change into gather and retain this
information via a new failure causes property (that is
lazily populated).

This will aid in the change to traceback2 and the
adjustments made in http://bugs.python.org/issue17911 so
that we can in the future use its exception class instead.

Change-Id: I8cadd7b70c2f638719155d96df4236fc40e18ccf
2015-03-10 10:03:58 -07:00
2013-11-22 11:25:03 +04:00
2014-01-07 18:10:43 +00:00
2014-02-07 20:45:32 +00:00
2013-09-17 13:27:27 -07:00
2013-05-07 10:49:44 -07:00
2013-07-07 21:46:32 -07:00
2015-02-21 08:58:35 -08:00
2014-01-02 10:38:15 -08:00
2014-05-01 12:43:52 +00:00
2015-02-12 16:03:29 -08:00

TaskFlow

Latest Version

Downloads

A library to do [jobs, tasks, flows] in a highly available, easy to understand and declarative manner (and more!) to be used with OpenStack and other projects.

Join us

Testing and requirements

Requirements

Because this project has many optional (pluggable) parts like persistence backends and engines, we decided to split our requirements into three parts: - things that are absolutely required (you can't use the project without them) are put into requirements-pyN.txt (N being the Python major version number used to install the package). The requirements that are required by some optional part of this project (you can use the project without them) are put into our tox.ini file (so that we can still test the optional functionality works as expected). If you want to use the feature in question (eventlet or the worker based engine that uses kombu or the sqlalchemy persistence backend or jobboards which have an implementation built using kazoo ...), you should add that requirement(s) to your project or environment; - as usual, things that required only for running tests are put into test-requirements.txt.

Tox.ini

Our tox.ini file describes several test environments that allow to test TaskFlow with different python versions and sets of requirements installed. Please refer to the tox documentation to understand how to make these test environments work for you.

Developer documentation

We also have sphinx documentation in docs/source.

To build it, run:

$ python setup.py build_sphinx
Description
RETIRED, further work has moved to Debian project infrastructure
Readme 4.8 MiB