This release is a pre-release and may not be stable for production use.
Flyte 2
Next-gen of SDK for Flyte.
Get started
- Only async tasks are supported right now. Style recommended,
import flyteand thenflyte.TaskEnvironmentetc - You have to create environment for even a single task
flyte runCLI does not yet support arguments (but will soon)- Support for dataclasses is still limited if present at all
- look at examples/... for various examples.
- For a single script recommend using uv run scripts with metadata headers.
Hello world
import flyte
env = flyte.TaskEnvironment(name="hello_world")
@env.task
async def say_hello(data: str) -> str:
return f"Hello {data}"
@env.task
async def say_hello_nested(data: str) -> str:
return await say_hello.override(resources=flyte.Resources(gpu="A100 80G:4")).execute(data)
if __name__ == "__main__":
import asyncio
# to run pure python - the SDK is not invoked at all
asyncio.run(say_hello_nested("test"))
# To run locally, but run through type system etc
flyte.init()
flyte.run(say_hello_nested, "World")
# To run remote
flyte.init(endpoint="dns:///localhost:8090", insecure=True)
flyte.run(say_hello_nested, "World")
# It is possible to switch local and remote, but keeping init to have and endpoint, but , changing context during run
flyte.with_runcontext(name="my-run-1", mode="local").run(...) # this will run locally only
When testing now, you will have to build images with v2 sdk installed.
To do this, you can use a nifty way to add the sdk to the image.
import flyte
import pathlib
env = flyte.TaskEnvironment(
name="test",
image=flyte.Image.auto(registry="ghcr.io/your-handle", name="package-name")
.with_source_folder(pathlib.Path(
__file__).parent.parent / "dist") # Assuming you have run `make dist` and the dist folder is in the directory above
.with_local_v2(), # This will add the v2 sdk to the image from the local dist folder
)
Run using CLI
flyte --endpoint dns:///localhost:8090 --insecure --org-override testorg run -p project -d development devbox_one.py say_hello_nested
Retrieve runs
flyte --endpoint dns:///localhost:8090 --insecure --org-override testorg get run --project testproject --domain development
Output:
┏━━━━━━━━━━━━━━━━━━━━━┳━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━┓
┃ Run-name ┃ Name ┃ Start_time ┃ End_time ┃ Run_time ┃ Phase ┃ Task ┃
┡━━━━━━━━━━━━━━━━━━━━━╇━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━┩
│ testrun │ a0 │ 2025-04-25T21:47:37.564471 │ None │ 41154 secs │ PHASE_QUEUED │ │
│ random-run-5783fbc8 │ a0 │ 2025-04-29T04:39:33.871810 │ 2025-04-29T04:42:24 │ 170 secs │ PHASE_SUCCEEDED │ │
│ random-run-e57d6195 │ a0 │ 2025-04-29T04:40:53.467206 │ 2025-04-29T04:42:54 │ 120 secs │ PHASE_SUCCEEDED │ say_hello_nested │
│ random-run-752c52a0 │ a0 │ 2025-04-29T04:44:50.169879 │ 2025-04-29T04:47:34 │ 163 secs │ PHASE_SUCCEEDED │ failure_recovery │
│ random-run-4f57d4af │ a0 │ 2025-04-29T05:04:28.780208 │ 2025-04-29T05:07:10 │ 161 secs │ PHASE_FAILED │ failure_recovery │
│ random-run-f6c6405f │ a0 │ 2025-04-29T05:10:19.808186 │ 2025-04-29T05:13:07 │ 167 secs │ PHASE_FAILED │ failure_recovery │
│ random-run-66448df4 │ a0 │ 2025-04-29T05:42:21.625827 │ 2025-04-29T05:45:01 │ 159 secs │ PHASE_SUCCEEDED │ failure_recovery │
│ random-run-5c5c905f │ a0 │ 2025-04-29T05:50:32.623097 │ 2025-04-29T05:53:21 │ 168 secs │ PHASE_SUCCEEDED │ failure_recovery │
│ random-run-99056dba │ a0 │ 2025-04-29T05:54:47.820520 │ 2025-04-29T05:57:31 │ 163 secs │ PHASE_SUCCEEDED │ failure_recovery │
└─────────────────────┴──────┴────────────────────────────┴─────────────────────┴────────────┴─────────────────┴──────────────────┘
Retrieve specific run details
flyte --endpoint dns:///localhost:8090 --insecure --org-override testorg get run --project testproject --domain development random-run-66448df4
Output:
RunDetails(name='random-run-66448df4', start_time='2025-04-29T05:42:21.625827', end_time='2025-04-29T05:45:01', run_time='159 secs', phase='PHASE_SUCCEEDED', error=, task='failure_recovery')
Retrieve actions for a run
flyte --endpoint dns:///localhost:8090 --insecure --org-override testorg get action --project testproject --domain development random-run-99056dba
Output:
┏━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━┓
┃ Run-name ┃ Name ┃ Start_time ┃ End_time ┃ Run_time ┃ Phase ┃ Task ┃
┡━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━┩
│ random-run-99056dba │ a0 │ 2025-04-29T05:54:47.820520 │ 2025-04-29T05:57:31 │ 163 secs │ PHASE_SUCCEEDED │ failure_recovery │
│ random-run-99056dba │ 5DYnhmntDf3WG9bm5B54E9 │ 2025-04-29T05:55:18.098842 │ 2025-04-29T05:55:51 │ 32 secs │ PHASE_FAILED │ always_fails │
│ random-run-99056dba │ 7rg3HTmTfCjMqhLLq17ZjR │ 2025-04-29T05:55:51.933307 │ 2025-04-29T05:56:31 │ 39 secs │ PHASE_FAILED │ always_fails │
│ random-run-99056dba │ 3avSConCJYUMmCuTpqUCdO │ 2025-04-29T05:56:31.939420 │ 2025-04-29T05:57:11 │ 39 secs │ PHASE_SUCCEEDED │ always_succeeds │
└─────────────────────┴────────────────────────┴────────────────────────────┴─────────────────────┴──────────┴─────────────────┴──────────────────┘
Retrieve action details
flyte --endpoint dns:///localhost:8090 --insecure --org-override testorg get action --project testproject --domain development random-run-99056dba 5DYnhmntDf3WG9bm5B54E9
Output:
ActionDetails(name='random-run-99056dba', start_time='2025-04-29T05:55:18.098842', end_time='2025-04-29T05:55:51', run_time='32 secs', phase='PHASE_FAILED', error=, task='always_fails')
Deploy
flyte deploy --endpoint dns:///localhost:8090 --insecure --org-override testorg -p project -d development devbox_one.py say_hello_nested
Contributor Notes
Some of these are limited to Union for now, because the new IDL has not yet been open-sourced.
How to import proto stubs?
Make sure that you have uv installed locally then run make copy-protos <path-to-cloud-repo>, where <path-to-cloud-repo>
is optional, if it's not defined then it assumes by default that there's a sibling cloud directory.
Iterating on the SDK itself.
While there is a publicly available semantically version base image (similar to flytekit) for each flyte sdk release, it's probably helpful to create your own images if you're to iterate on this SDK itself. Anyone who wishes to modify this code and then run it on a Flyte cluster, will need to build their own image.
To do this:
-
Build a wheel with your updated code by running
make dist -
(This step only works for Union employees for now) Create the image by running
python maint_tools/build_default_image.py
This will build the image using buildx, creating a buildx builder. The image will be tagged with a SHA that changes based on a hash of the built wheel inside the dist folder.
Metadata
Release files for flyte 0.2.0b1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| flyte-0.2.0b1-py3-none-any.whl | Python 3 | none | any | Details for flyte-0.2.0b1-py3-none-any.whl |
Release files / flyte-0.2.0b1-py3-none-any.whl
| Download URL | flyte-0.2.0b1-py3-none-any.whl |
|---|---|
| Size | 319.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6b5d8b1b833244323ea7e8a0000f13065cfa3029a2e5091bd0f7bd7f0977564a
|
|
BLAKE2b-256 checksum How to use checksums |
c38311d813cda938206853f3cf4d4411aced586fd038ffd39b1bf209249352ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for flyte 0.2.0b1
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.