ActionTree is a Python (3.5+) library to execute (long) actions in parallel, respecting dependencies between those actions. You create a dependency graph of actions to be executed and then call the execute function on its root.
It’s licensed under the MIT license. It’s available on the Python package index. Its documentation and its source code are on GitHub.
Questions? Remarks? Bugs? Want to contribute? Open an issue!
Quick start
Install from PyPI:
$ pip install ActionTree
With dependencies to create Gantt charts and dependency graphs:
$ pip install 'ActionTree[dependency_graphs,gantt]'
Import:
>>> from ActionTree import execute >>> from ActionTree.stock import CallSubprocess
Execute some action:
>>> link = CallSubprocess(["g++", "a.o", "b.o", "-o", "test"]) >>> link.add_dependency(CallSubprocess(["g++", "-c", "a.cpp", "-o", "a.o"])) >>> link.add_dependency(CallSubprocess(["g++", "-c", "b.cpp", "-o", "b.o"])) >>> report = execute(link)
And verify everything went well:
>>> report.is_success
True
>>> os.path.isfile("test")
True
Metadata
Release files for ActionTree 0.13.2
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 |
|---|---|---|---|---|
| ActionTree-0.13.2.tar.gz | 19.6 kB | Without provenance | Details for ActionTree-0.13.2.tar.gz |
Release files / ActionTree-0.13.2.tar.gz
| Download URL | ActionTree-0.13.2.tar.gz |
|---|---|
| Size | 19.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
803dd52c365de24513c4665a855c4702d2069b8a38c9f812bd034f71ebc9f5a5
|
|
BLAKE2b-256 checksum How to use checksums |
545fc1ed6be040a71071104c58f3fe388b0d72b360c3422c673ee6a6358930e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.4.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.7
|
Security for ActionTree 0.13.2
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.