Kryo Python SDK
Python helper for Kryo checkpoint signaling. It is optional: other languages send SIGUSR1 / wait for SIGUSR2, or use kryo snapshot create --wait.
kryo.checkpoint() does not snapshot by itself. The Kryo CLI freezes the process after it receives that signal.
Installation
pip install kryo
You still need the Kryo CLI, CRIU, and cuda-checkpoint on Linux. kryo snapshot create and kryo run must be run as root (sudo).
Usage
import kryo
# Setup (runs once, gets checkpointed)
model = load_model()
model.to("cuda")
kryo.checkpoint() # Freeze here
# Inference (runs after restore)
result = model(input)
Then:
sudo kryo snapshot create --name mymodel -- python app.py
sudo kryo run --snapshot mymodel
checkpoint() is idempotent. Recreate the snapshot when the code, model, CUDA toolkit, or NVIDIA driver changes.
Requirements
- Linux (CRIU is Linux-only)
- Kryo CLI on
PATH - NVIDIA driver 550+ for GPU checkpointing
- CRIU and
cuda-checkpoint
1 maintainer
Metadata
1 maintainer
Release files for kryo 0.4.1
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 |
|---|---|---|---|---|
| kryo-0.4.1.tar.gz | 29.4 kB | With provenance | Details for kryo-0.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kryo-0.4.1-py3-none-any.whl | Python 3 | none | any | Details for kryo-0.4.1-py3-none-any.whl |
Total release size: 32.5 kB
Release files / kryo-0.4.1.tar.gz
| Download URL | kryo-0.4.1.tar.gz |
|---|---|
| Size | 29.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
562a3e8a5e99b93e386ccc95f679253b8ff759d723fff16b2eeb70270349928b
|
|
BLAKE2b-256 checksum How to use checksums |
79c653145cfdedc8109433493b7630f692ef9c8a786ce27111213d36d52da474
|
| 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 Aug 31, 2026.
Transparency logRelease files / kryo-0.4.1-py3-none-any.whl
| Download URL | kryo-0.4.1-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a1bdb514525158204c24cf9e701783ba329d41bd69c1b2d04edf69fd434c051e
|
|
BLAKE2b-256 checksum How to use checksums |
77aeed631c2c55c0a6056b485562979cb1062d5a6ed14dd6d52ccda9110e187d
|
| 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 Aug 31, 2026.
Transparency logSecurity for kryo 0.4.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for kryo-0.4.1.tar.gz
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 Aug 31, 2026.
Transparency logA 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.
