flytezen
A template for hydra-zen configuration of Flyte workflow execution.
Quick start
See make | grep codespace, run make codespace_create code, or
This provides a zero install demonstration of the supported development environment that depends on the nix package manager or open container images built with it. See make | grep nix or make -n setup_dev to setup a local copy of this environment.
Layout
tree
.
├── .argo
│ └── build.yaml
├── .devcontainer
│ ├── devcontainer.Dockerfile
│ └── devcontainer.json
├── .flyte
│ ├── config-browser.yaml
│ ├── config-local.yaml
│ ├── config-template.yaml
│ └── config.yaml
├── .github
│ ├── actions
│ │ ├── setup_environment
│ │ │ └── action.yml
│ │ └── tag-build-push-container
│ ├── disabled
│ │ ├── CD.yaml
│ │ └── CI.yaml
│ ├── workflows
│ │ ├── CID.yaml
│ │ ├── build-images.yaml
│ │ └── labeler.yml
│ ├── .gitkeep
│ ├── CODEOWNERS
│ ├── codecov.yml
│ ├── labels.yml
│ └── renovate.json
├── .vscode
│ ├── extensions.json
│ ├── launch.json
│ ├── settings.json
│ └── tasks.json
├── containers
│ ├── Dockerfile
│ ├── compose.yaml
│ ├── gpu.Dockerfile
│ └── pkg.Dockerfile
├── docs
│ ├── notebooks
│ │ └── text
│ ├── reference
│ │ └── flytezen.md
│ ├── index.md
│ └── specification.md
├── environments
│ └── conda
│ ├── conda-linux-64.lock.yml
│ ├── conda-lock.yml
│ └── virtual-packages.yml
├── src
│ ├── flytezen
│ │ ├── cli
│ │ │ ├── __init__.py
│ │ │ ├── execute.py
│ │ │ ├── execution_config.py
│ │ │ └── execution_utils.py
│ │ ├── workflows
│ │ │ ├── __init__.py
│ │ │ ├── example.py
│ │ │ └── lrwine.py
│ │ ├── __init__.py
│ │ ├── __main__.py
│ │ ├── configuration.py
│ │ ├── constants.py
│ │ └── logging.py
│ └── .gitkeep
├── tests
│ ├── __init__.py
│ ├── conftest.py
│ └── test_cli.py
├── .dockerignore
├── .env
├── .envrc
├── .example.env
├── .gitignore
├── CHANGELOG.md
├── LICENSE
├── Makefile
├── README.md
├── devshell
├── flake.lock
├── flake.nix
├── mkdocs.yml
├── poetry.lock
├── poetry.toml
├── pyproject.toml
└── requirements.txt
23 directories, 65 files
Acknowledgements
Selected dependencies
See also flake.nix, pyproject.toml, and .github.
Metadata
Release files for flytezen 1.0.3
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 |
|---|---|---|---|---|
| flytezen-1.0.3.tar.gz | 36.1 kB | Without provenance | Details for flytezen-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flytezen-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for flytezen-1.0.3-py3-none-any.whl |
Total release size: 73.6 kB
Release files / flytezen-1.0.3.tar.gz
| Download URL | flytezen-1.0.3.tar.gz |
|---|---|
| Size | 36.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
885cce3f7f8679c05e32307e3361feeaa677208f409c1a541a13573c593dd229
|
|
BLAKE2b-256 checksum How to use checksums |
da73b26f427a69c4fceb4f827952ed44c44e12e836b2efb760b5c87be0bd6386
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Release files / flytezen-1.0.3-py3-none-any.whl
| Download URL | flytezen-1.0.3-py3-none-any.whl |
|---|---|
| Size | 37.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed56dd0643a59d6e0f80c338a9aa545493e591cbd448984cca49170596c4d494
|
|
BLAKE2b-256 checksum How to use checksums |
74ea1e38e082009c7cbf8ed3e80377f6c309f5f6b8e36688fbbd8cdbcf5c4020
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.7
|
Security for flytezen 1.0.3
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.