bbp-workflow
Automated pipelines of batch jobs using python and the luigi framework.
Documentation
Installation
bbp-workflow can be pip installed with the following command:
$ pip install bbp-workflowTests
pip install tox
toxLocal Run
make install_to_venv
./bbp-workflow-launch.sh --config workflows/foo.cfg foo Bar dynamic-param=worldAcknowledgements
The development of this software was supported by funding to the Blue Brain Project, a research center of the École polytechnique fédérale de Lausanne (EPFL), from the Swiss government’s ETH Board of the Swiss Federal Institutes of Technology.
For license and authors, see LICENSE.txt and AUTHORS.txt respectively.
Copyright (c) 2022-2024 Blue Brain Project/EPFL
2 maintainers
Metadata
2 maintainers
Release files for bbp-workflow 4.1.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 |
|---|---|---|---|---|
| bbp_workflow-4.1.2.tar.gz | 79.8 kB | Without provenance | Details for bbp_workflow-4.1.2.tar.gz |
Release files / bbp_workflow-4.1.2.tar.gz
| Download URL | bbp_workflow-4.1.2.tar.gz |
|---|---|
| Size | 79.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79675fbc372f036f8d1fc5da46f540a92736e095a77fdf88bdfdfc67be21c30a
|
|
BLAKE2b-256 checksum How to use checksums |
796a3b283702064a6593f99d59a41b5c53c9f2625f3e4920d74b8bc9633be570
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Security for bbp-workflow 4.1.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.
