Ties your debbuging workflow to automated workflows elsewhere
Project description
Sewerpipe
Sewerpipe lets you define workflows based entirely on running Python modules as tasks:
from sewer.config import Task
from sewer.workflows import workflow
t1 = Task(
name="Example 1",
module="sewer.dummy",
parameters_and_flags=dict(
verbose=True,
name="My momma"
)
)
t2 = Task(
name="Example 2",
module="sewer.dummy",
parameters_and_flags=dict(
verbose=False,
name="My momma not"
)
)
@workflow
def workflow():
(t1 >> t2).run()
def main():
workflow()
if __name__ == "__main__":
main()
The syntax is similar to Airflow DAGs, quite intentionally. There are three ways to use it:
- Direct triggering of workflows via
sppe run
- Conversion of the defined workflows to VSCode
launch.json
, so that your debug configuration is up to date with what is defined as a single-source-of-truth workflow (sppe convert --to vscode
) - Library use to enable seamless creation of Airflow DAGs (via the
airflow.create_airflow_tasks
function)
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
sewerpipe-0.1.0.tar.gz
(4.3 kB
view hashes)
Built Distribution
Close
Hashes for sewerpipe-0.1.0-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | ca6f7cab7462123e520f2a258b598f4448cf32dd3ac68c584ef56fb311672059 |
|
MD5 | 0a386d355618e9e1f66fc1342f72dcf4 |
|
BLAKE2b-256 | 1b4d176d272d64a78fac1c2cd56e10fc006b887081347b960c9dc75dcca4f756 |