Cadence Python SDK
Cadence is a distributed, scalable, durable, and highly available orchestration engine we developed at Uber Engineering to execute asynchronous long-running business logic in a scalable and resilient way.
If you'd like to propose a new feature, first join the CNCF Slack workspace in the #cadence-users channel to start a discussion.
The Cadence Python SDK is the framework for authoring workflows and activities using the Python programming language.
Installation
Install from PyPI:
pip install cadence-python-client
Or with uv:
uv add cadence-python-client
The core package supports Python >=3.11,<3.14.
The SDK is ready for production use using PYPI. To build from source, clone the repository and install the development dependencies.
Clone the repository if you want to develop locally:
git clone https://github.com/cadence-workflow/cadence-python-client.git
cd cadence-python-client
Development
Setup
-
Install protobuf (required):
# macOS brew install protobuf@29 # Linux/Other # Install protobuf 29.x via your package manager
-
Install uv (recommended):
# macOS brew install uv # Linux/Other curl -LsSf https://astral.sh/uv/install.sh | sh source $HOME/.local/bin/env # Add to your shell profile for persistence
-
Create virtual environment and install dependencies:
uv sync --all-extras
Or if you prefer traditional pip:
python3.11 -m venv venv source venv/bin/activate # Windows: venv\Scripts\activate pip install -e ".[dev]"
Generate Protobuf and gRPC Files
Run the generation script only if you change files under idls/proto/:
# Recommended
make generate
# Or run the script directly
uv run python scripts/generate_proto.py
This will:
- Generate Python protobuf files in
cadence/api/v1/ - Generate gRPC service files in
cadence/api/v1/ - Refresh the package imports for the generated modules
Test
Run the main checks:
make lint
make type-check
make test
Run integration tests with Docker:
make integration-test
You can also verify the generated files manually:
uv run python cadence/sample/simple_usage_example.py
uv run python cadence/sample/grpc_usage_example.py
Development Commands
The current repository workflow is centered on make targets:
make install
make generate
make lint
make type-check
make test
make integration-test
make pr
License
Apache 2.0 License, please see LICENSE for details.
Release files for cadence-python-client 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cadence_python_client-0.4.0.tar.gz | 553.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cadence_python_client-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 924.6 kB
Release files / cadence_python_client-0.4.0.tar.gz
| Download URL | cadence_python_client-0.4.0.tar.gz |
|---|---|
| Size | 553.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05892516f696e12c9693dbd871828d62def15f516a8f5785ba927b8648836a3a
|
|
BLAKE2b-256 checksum How to use checksums |
c1d079d2b762b0be4e41e834cf4f20412abad65cd004ebed3fad55fda7add709
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency logRelease files / cadence_python_client-0.4.0-py3-none-any.whl
| Download URL | cadence_python_client-0.4.0-py3-none-any.whl |
|---|---|
| Size | 371.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
40d484fe75fae57c0ba85ff816b927a071fed4b97dab9493e158666a976a692b
|
|
BLAKE2b-256 checksum How to use checksums |
78f712aca4b7cd46cd34bf17d40c487d5c0ce49004051d63c60bf2ae38b18869
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency log