XWorkflows is a library to add workflows, or state machines, to Python objects.
It has been fully tested with Python 2.7 and all versions from 3.4 to 3.9
Links
Package on PyPI: http://pypi.python.org/pypi/xworkflows
Repository and issues on GitHub: http://github.com/rbarrois/xworkflows
Example
It allows to easilly define a workflow, attach it to a class, and use its transitions:
import xworkflows
class MyWorkflow(xworkflows.Workflow):
# A list of state names
states = (
('foo', "Foo"),
('bar', "Bar"),
('baz', "Baz"),
)
# A list of transition definitions; items are (name, source states, target).
transitions = (
('foobar', 'foo', 'bar'),
('gobaz', ('foo', 'bar'), 'baz'),
('bazbar', 'baz', 'bar'),
)
initial_state = 'foo'
class MyObject(xworkflows.WorkflowEnabled):
state = MyWorkflow()
@xworkflows.transition()
def foobar(self):
return 42
# It is possible to use another method for a given transition.
@xworkflows.transition('gobaz')
def blah(self):
return 13
>>> o = MyObject()
>>> o.state
<StateWrapper: <State: 'foo'>>
>>> o.state.is_foo
True
>>> o.state.name
'foo'
>>> o.state.title
'Foo'
>>> o.foobar()
42
>>> o.state
<StateWrapper: <State: 'bar'>>
>>> o.state.name
'bar'
>>> o.state.title
'Bar'
>>> o.blah()
13
>>> o.state
<StateWrapper: <State: 'baz'>>
>>> o.state.name
'baz'
>>> o.state.title
'Baz'
Hooks
Custom functions can be hooked to transactions, in order to run before/after a transition, when entering a state, when leaving a state, …:
class MyObject(xworkflows.WorkflowEnabled):
state = MyWorkflow()
@xworkflows.before_transition('foobar')
def my_hook(self, *args, **kwargs):
# *args and **kwargs are those passed to MyObject.foobar(...)
pass
@xworkflows.on_enter_state('bar')
def my_other_hook(self, result, *args, **kwargs):
# Will be called just after any transition entering 'bar'
# result is the value returned by that transition
# *args, **kwargs are the arguments/keyword arguments passed to the
# transition.
pass
Metadata
Release files for xworkflows 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| xworkflows-1.1.0.tar.gz | 39.4 kB | Without provenance | Details for xworkflows-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| xworkflows-1.1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for xworkflows-1.1.0-py2.py3-none-any.whl |
Total release size: 52.9 kB
Release files / xworkflows-1.1.0.tar.gz
| Download URL | xworkflows-1.1.0.tar.gz |
|---|---|
| Size | 39.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e3a9f6e9de6bcd779335f2ce4f87445ad8047771be9c6c96e347fb8622e2f27
|
|
BLAKE2b-256 checksum How to use checksums |
d2ffb49f4422f2406b790e468a758acc46d80fc7fdbfbd1d55297617ee8a0efa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.8
|
Release files / xworkflows-1.1.0-py2.py3-none-any.whl
| Download URL | xworkflows-1.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 13.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
943571904066e03946016c5710cfea97847c1931c2e07bdd61827a01bce38d80
|
|
BLAKE2b-256 checksum How to use checksums |
2e1349ba48867b92bca3b277abe45810f2dc440df8c1df38de2c23a8b52171c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.8
|
Security for xworkflows 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.