Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Dynamo Python Bindings

Python bindings for the Dynamo runtime system, enabling distributed computing capabilities for machine learning workloads.

🚀 Quick Start

  1. Install uv: https://docs.astral.sh/uv/#getting-started
curl -LsSf https://astral.sh/uv/install.sh | sh
  1. Install protoc protobuf compiler: https://grpc.io/docs/protoc-installation/.

For example on an Ubuntu/Debian system:

apt install protobuf-compiler
  1. Setup a virtualenv
uv venv
source .venv/bin/activate
uv pip install 'maturin[patchelf]'
  1. Build and install dynamo wheel
maturin develop --uv

Run Examples

Prerequisite

See README.md.

Hello World Example

  1. Start 3 separate shells, and activate the virtual environment in each
source .venv/bin/activate
  1. In one shell (shell 1), run example server the instance-1
python3 ./examples/hello_world/server.py
  1. (Optional) In another shell (shell 2), run example the server instance-2
python3 ./examples/hello_world/server.py
  1. In the last shell (shell 3), run the example client:
python3 ./examples/hello_world/client.py

If you run the example client in rapid succession, and you started more than one server instance above, you should see the requests from the client being distributed across the server instances in each server's output. If only one server instance is started, you should see the requests go to that server each time.

Performance

The performance impacts of synchronizing the Python and Rust async runtimes is a critical consideration when optimizing the performance of a highly concurrent and parallel distributed system.

The Python GIL is a global critical section and is ultimately the death of parallelism. To compound that, when Rust async futures become ready, accessing the GIL on those async event loop needs to be considered carefully. Under high load, accessing the GIL or performing CPU intensive tasks on on the event loop threads can starve out other async tasks for CPU resources. However, performing a tokio::task::spawn_blocking is not without overheads as well.

If bouncing many small message back-and-forth between the Python and Rust event loops where Rust requires GIL access, this is pattern where moving the code from Python to Rust will give you significant gains.

Metadata

Release files for ai-dynamo-runtime 1.6.0.dev20261023

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for ai-dynamo-runtime 1.6.0.dev20261023
File Interpreter ABI Platform Actions
ai_dynamo_runtime-1.6.0.dev20261023-cp311-abi3-manylinux_2_28_x86_64.whl CPython 3.11 abi3 Linux glibc 2.28+ x86-64 Details for ai_dynamo_runtime-1.6.0.dev20261023-cp311-abi3-manylinux_2_28_x86_64.whl
ai_dynamo_runtime-1.6.0.dev20261023-cp311-abi3-manylinux_2_28_aarch64.whl CPython 3.11 abi3 Linux glibc 2.28+ ARM64 Details for ai_dynamo_runtime-1.6.0.dev20261023-cp311-abi3-manylinux_2_28_aarch64.whl

Total release size: 152.2 MB

Release files / ai_dynamo_runtime-1.6.0.dev20261023-cp311-abi3-manylinux_2_28_x86_64.whl

Download URL ai_dynamo_runtime-1.6.0.dev20261023-cp311-abi3-manylinux_2_28_x86_64.whl
Size 76.8 MB
Tags CPython 3.11 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
0b5e85a6a47d4c2411d74f7166f934ab2f138ece5093de44b290d74883f3b47c
BLAKE2b-256 checksum
How to use checksums
662f4d89ca8f44e4c7090ed7b419fbe67595e91969eb835eb7f266b0e5c612e9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.8

Release files / ai_dynamo_runtime-1.6.0.dev20261023-cp311-abi3-manylinux_2_28_aarch64.whl

Download URL ai_dynamo_runtime-1.6.0.dev20261023-cp311-abi3-manylinux_2_28_aarch64.whl
Size 75.4 MB
Tags CPython 3.11 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
4a1da693b5d0f8ea8d333a2c1fb8c15e6a8112b75a2c0de4b607600b4f2e5b38
BLAKE2b-256 checksum
How to use checksums
6645b8f86e1ba4e568794296ab8cf9769564b62018d10a357552308b75652ed9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.8

Security for ai-dynamo-runtime 1.6.0.dev20261023

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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page