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.8.0.dev20261119

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.8.0.dev20261119
File Interpreter ABI Platform Actions
ai_dynamo_runtime-1.8.0.dev20261119-cp311-abi3-manylinux_2_28_x86_64.whl CPython 3.11 abi3 Linux glibc 2.28+ x86-64 Details for ai_dynamo_runtime-1.8.0.dev20261119-cp311-abi3-manylinux_2_28_x86_64.whl
ai_dynamo_runtime-1.8.0.dev20261119-cp311-abi3-manylinux_2_28_aarch64.whl CPython 3.11 abi3 Linux glibc 2.28+ ARM64 Details for ai_dynamo_runtime-1.8.0.dev20261119-cp311-abi3-manylinux_2_28_aarch64.whl

Total release size: 173.5 MB

Release files / ai_dynamo_runtime-1.8.0.dev20261119-cp311-abi3-manylinux_2_28_x86_64.whl

Download URL ai_dynamo_runtime-1.8.0.dev20261119-cp311-abi3-manylinux_2_28_x86_64.whl
Size 87.5 MB
Tags CPython 3.11 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
6dd472b7d9670a2d4a262621374f06c9c499ae7d5824ebcd690749424ac49b4c
BLAKE2b-256 checksum
How to use checksums
c2df010ebfa7963f30350d60e16e417c8ebf1ca633dbfaab55a9c9dc5442f4bc
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.8.0.dev20261119-cp311-abi3-manylinux_2_28_aarch64.whl

Download URL ai_dynamo_runtime-1.8.0.dev20261119-cp311-abi3-manylinux_2_28_aarch64.whl
Size 86.0 MB
Tags CPython 3.11 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
33c93d561f684d16913537dc4b07e6747feaa1ad2289339f68eec2fafff90532
BLAKE2b-256 checksum
How to use checksums
0f8fa8ef91075fa71eb4487965cabda42e43dd2345d1d19dd9e437d2325b7ed1
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.8.0.dev20261119

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