Go to file
Joshua Harlow 40cf88e55c Expose strategies so doc generation can easily pick them up
Since we have put a warning on the engine components docs saying
they should not be used externally it seems ok to make these more
visible so that people reading the docs can follow more of how it
works (and the components involved there-in).

Depends-On: I0f07858e96ea3baf46f8a453e253b9ed29c7f7e2

Depends-On: I33bd2d9dff9cb7dc1a50177db7286b7317966784

Change-Id: I24d5cbfd47aa786ffab923243b97c7ae43b2f21f
2015-07-06 00:09:50 +00: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
2014-01-02 10:38:15 -08:00
2015-03-09 11:25:22 -07:00
2015-06-22 08:28:48 +00: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