A previous release had provenance metadata, but this release does not. View details.
Quick Start • Installation • Contributing • Documentation
pyflow-wellies
[!IMPORTANT] This software is Incubating and subject to ECMWF's guidelines on Software Maturity.
Wellies provides extra features to help you build consistent and configurable pyflow suites. This guide assumes a good level of familiarity with ecflow suites and using pyflow for its design and generation. Please refer to these projects' documentantion if some point about them is not clear.
Features
- YAML-based configuration for your suites: wellies provides simple patterns to help configuring your suite, making them more flexible and suitable for different use cases and environments.
- Simple template to start your suite design from scratch: Don't get blocked
by a blanck page; with
wellies-quickstartstarting to code a new workflow is one command away. - Git-tracked suite deployment from tracksuite: Wellies comes fully integrated with tracksuite providing git-based changes control for multi-users and remote deployment environments.
- Extended pyflow nodes for improved suite design, configuration and monitoring.
- Template scripts for improved reproducibility and support to D-R-Y design when it comes to scripting, like when dealing with datetime objects, MARS requests and others.
Quick Start
To create an empty suite with the default wellies structure, simply run
wellies-quickstart /path/to/project -p mysuite
Once created the suite can be build with:
cd /path/to/project
./mysuite.py configs/*.yaml
which is equivalent to
./mysuite.py configs/config.yaml config/tools.yaml configs/data.yaml config/execution_contexts.yaml
You can also cherry pick your configuration files following your needs:
cd /path/to/project
./mysuite.py configs/config.yaml config/tools.yaml
Alternatively you use named preset groups of configurations defined in a default Makefile and just use
make
Installation
First you need to assure you have ecFlow installed on your system. The simplest way is to create a conda environment. We recommend using mamba to speed up the environment creation process:
mamba create -c conda-forge -n wellies-env python=3.10 ecflow
conda activate wellies-env
Install from the Github repository directly:
python -m pip install https://github.com/ecmwf/pyflow-wellies
or from PyPI:
python -m pip install pyflow-wellies
License
See LICENSE
In applying this licence, ECMWF does not waive the privileges and immunities
granted to it by virtue of its status as an intergovernmental organisation
nor does it submit to any jurisdiction.
Copyright
© 2023 ECMWF. All rights reserved.
Contributing
First build a development conda environment
mamba env create -f ./environment.yml -n wellies-env
conda activate wellies-env
Then install with development dependencies
git clone https://github.com/ecmwf/pyflow-wellies.git
cd pyflow-wellies
pip install -e .[dev]
Building package
To build source distributions, build is required. With that the source distribution can be built from any environment with
git clone https://github.com/ecmwf/pyflow-wellies.git
cd pyflow-wellies
python -m build
Testing
To run tests, first install testing dependencies:
git clone https://github.com/ecmwf/pyflow-wellies.git
cd pyflow-wellies
pip install .[test]
Then to run all tests
python -m pytest
Documentation
To build your own local documentation you need mkdocs and a few entra plugins. As there are many auto-generated parts in the documentation, you will need a environment with wellies and all of its dependencies installed to build the documentation. To install the documentation-only dependencies:
git clone https://github.com/ecmwf/pyflow-wellies.git
cd pyflow-wellies
pip install .[docs]
Then to build it
mkdocs build
To build and make it available in a local server
mkdocs serve
Metadata
Release files for pyflow-wellies 1.3.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyflow_wellies-1.3.1.0.tar.gz | 189.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyflow_wellies-1.3.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 370.1 kB
Release files / pyflow_wellies-1.3.1.0.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | pyflow_wellies-1.3.1.0.tar.gz |
|---|---|
| Size | 189.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38617924b857998fb55d73026ea21e5c863d7728e99420b0304e06af1cc3e910
|
|
BLAKE2b-256 checksum How to use checksums |
726884ef625c7013863024f3692ef102b7f46af3343ebcdf7049d516d3f92ca4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Release files / pyflow_wellies-1.3.1.0-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | pyflow_wellies-1.3.1.0-py3-none-any.whl |
|---|---|
| Size | 181.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2f088b5c8aa3f3f80da5a933badbbf6d8ef3b210611ecb982349614aad61d35
|
|
BLAKE2b-256 checksum How to use checksums |
ced9490fb340ae4ababa46181033e3162102aa1986dd6de5da41e1299fcfe1d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Security for pyflow-wellies 1.3.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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 1.3.0 2 files With provenance
- Added 1.3.1.0 2 files Without provenance
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.