checkpoint-engine 0.1.2__tar.gz

checkpoint_engine-0.1.2/.github/workflows/pre-commit.yaml

@@ -0,0 +1,22 @@
+name: pre-commit
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    types: [opened, synchronize, reopened]
+
+jobs:
+  pre-commit:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: '3.x'
+      - name: Run pre-commit hooks
+        uses: pre-commit/action@v3.0.1
+        with:
+          extra_args: --all-files

checkpoint_engine-0.1.2/.github/workflows/python-publish.yml

@@ -0,0 +1,70 @@
+# This workflow will upload a Python Package to PyPI when a release is created
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries
+
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+name: Upload Python Package
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  release-build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Build release distributions
+        run: |
+          # NOTE: put your own distribution build steps here.
+          python -m pip install build
+          python -m build
+
+      - name: Upload distributions
+        uses: actions/upload-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+  pypi-publish:
+    runs-on: ubuntu-latest
+    needs:
+      - release-build
+    permissions:
+      # IMPORTANT: this permission is mandatory for trusted publishing
+      id-token: write
+
+    # Dedicated environments with protections for publishing are strongly recommended.
+    # For more information, see: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-protection-rules
+    environment:
+      name: pypi
+      # OPTIONAL: uncomment and update to include your PyPI project URL in the deployment status:
+      # url: https://pypi.org/p/YOURPROJECT
+      #
+      # ALTERNATIVE: if your GitHub Release name is the PyPI project version string
+      # ALTERNATIVE: exactly, uncomment the following line instead:
+      # url: https://pypi.org/project/YOURPROJECT/${{ github.event.release.name }}
+
+    steps:
+      - name: Retrieve release distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+      - name: Publish release distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/

checkpoint_engine-0.1.2/.gitignore

@@ -0,0 +1,13 @@
+*.pyc
+/.python-version
+/uv.lock
+*.egg-info
+.pytest_cache
+.coverage
+.mypy_cache
+.ruff_cache
+.DS_Store
+.idea
+build/
+dist/
+_version.py

checkpoint_engine-0.1.2/.pre-commit-config.yaml

@@ -0,0 +1,32 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: check-symlinks
+      - id: destroyed-symlinks
+      - id: trailing-whitespace
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-toml
+      - id: check-ast
+      - id: check-added-large-files
+      - id: check-merge-conflict
+      - id: check-executables-have-shebangs
+      - id: check-shebang-scripts-are-executable
+      - id: detect-private-key
+      - id: debug-statements
+      - id: check-added-large-files
+        args: [--maxkb=10240]
+  - repo: https://github.com/charliermarsh/ruff-pre-commit
+    rev: v0.12.2
+    hooks:
+      - id: ruff
+        args: [--fix, --exit-non-zero-on-fix]
+      - id: ruff-format
+  - repo: https://github.com/codespell-project/codespell
+    rev: v2.4.1
+    hooks:
+      - id: codespell
+        additional_dependencies: [".[toml]"]
+
+exclude: ^patches

checkpoint_engine-0.1.2/LICENCE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Moonshot AI
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE

checkpoint_engine-0.1.2/PKG-INFO

@@ -0,0 +1,176 @@
+Metadata-Version: 2.4
+Name: checkpoint-engine
+Version: 0.1.2
+Summary: checkpoint-engine is a lightweight, decoupling and efficient weight update middleware
+Project-URL: Homepage, https://github.com/MoonshotAI/checkpoint-engine
+Project-URL: Repository, https://github.com/MoonshotAI/checkpoint-engine
+Project-URL: Documentation, https://github.com/MoonshotAI/checkpoint-engine
+Project-URL: Issue Tracker, https://github.com/MoonshotAI/checkpoint-engine/issues
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENCE
+Requires-Dist: torch>=2.5.0
+Requires-Dist: fastapi
+Requires-Dist: pydantic>=2.0.0
+Requires-Dist: safetensors
+Requires-Dist: pyzmq
+Requires-Dist: uvicorn
+Requires-Dist: loguru
+Requires-Dist: numpy
+Requires-Dist: httpx
+Provides-Extra: p2p
+Requires-Dist: mooncake-transfer-engine>=0.3.5; extra == "p2p"
+Dynamic: license-file
+
+# Checkpoint Engine
+Checkpoint-engine is a simple middleware to update model weights in LLM inference engines -- a critical step in reinforcement learning.
+We provide an efficient and lightweight implementation for inplace weight update:
+updating our [Kimi-K2](https://github.com/MoonshotAI/Kimi-K2) model (1 Trillion parameters) across thousands of GPUs takes about 20s.
+
+
+<div align="center">
+  <picture>
+      <img src="figures/checkpoint-engine.png" width="80%" alt="ckpt-engine">
+  </picture>
+</div>
+
+## Architecture
+
+The core weight update logic is in `ParameterServer` class, a service colocated with inference engines. It provides two implementations of weight update: Broadcast and P2P.
+
+- **Broadcast**: Used when a large number of inference instances need to update weights in synchronous. This is the fastest implementation and should be used as the default update method. See `_update_per_bucket`.
+- **P2P**: Used when new inference instances are dynamically added (due to restarts or dynamic availability) while the existing instances are already serving requests. Under this scenario, to avoid affecting the workloads on existing instances, we use the [`mooncake-transfer-engine`](https://github.com/kvcache-ai/Mooncake?tab=readme-ov-file#use-python-package) to P2P send weights from CPUs in existing instances to GPUs in new instances. See `_update_per_bucket_p2p`.
+
+### Optimized Weight Broadcast
+In the *Broadcast* implementation, the checkpoint-engine holds references to sharded weights in CPU memory, and need to efficiently broadcast them to a cluster of inference instances, often under a different sharding pattern.
+We arrange the data transfer into 3 stages:
+1. H2D: moving weights to GPU memory. These weights may come from disk or the training engine.
+2. broadcast: broadcast among checkpoint engine workers; the data results in a CUDA IPC buffer shared with inference engine.
+3. reload: inference engine decides what subset of weights to copy from the broadcasted data.
+
+Checkpoint-engine orchestrates the entire transfer process. It first gathers necessary metadata to create a plan, including deciding the proper bucket size for data transfer.
+It then executes the transfer, where it controls the inference engine through a ZeroMQ socket. To maximize performance, it organizes the data transfers into a pipeline with overlapped communication and copy, illustrated below. The details can be found in [Kimi-K2 Technical Report](https://arxiv.org/abs/2507.20534).
+
+
+<div align="center">
+  <picture>
+      <img src="figures/pipeline.png" width="80%" alt="pipeline">
+  </picture>
+</div>
+
+Pipelining naturally requires more GPU memory. When memory is not enough, checkpoint-engine will fallback to serial execution.
+
+## Benchmark
+
+| Model                                | Device Info  | GatherMetas | Update (Broadcast) | Update (P2P)            |
+| :----------------------------------- | :----------- | :---------- |:-------------------| :---------------------- |
+| GLM-4.5-Air (BF16)                   | 8xH800 TP8  | 0.17s       | 3.94s (1.42GiB)    | 8.83s (4.77GiB)         |
+| Qwen3-235B-A22B-Instruct-2507 (BF16) | 8xH800 TP8  | 0.46s       | 6.75s (2.69GiB)    | 16.47s (4.05GiB)        |
+| DeepSeek-V3.1 (FP8)                  | 16xH20 TP16  | 1.44s       | 12.22s (2.38GiB)   | 25.77s (3.61GiB)        |
+| Kimi-K2-Instruct (FP8)               | 16xH20 TP16  | 1.81s       | 15.45s (2.93GiB)   | 36.24s (4.46GiB)        |
+| DeepSeek-V3.1 (FP8)                  | 256xH20 TP16 | 1.40s       | 13.88s (2.54GiB)   | 33.30s (3.86 GiB) |
+| Kimi-K2-Instruct (FP8)               | 256xH20 TP16 | 1.88s       | 21.50s (2.99GiB)   | 34.49s (4.57 GiB) |
+
+All results above are tested by [`examples/update.py`](./examples/update.py) and use [vLLM v0.10.2rc1](https://github.com/vllm-project/vllm/tree/v0.10.2rc1) as inference engine. Some notes:
+
+* FP8 test needs additional vLLM patches, see [FP8 quantization](#fp8-quantization).
+* Device Info: we tested various combination of devices and parallelism setups. For example, a 256-GPU TP16 setup means that we deploy 16 vLLM instances, each with 16-way tensor parallelism.
+* Since update duration is related to IPC bucket size, we provide the bucket size in the table.
+* The P2P time were tested for updating no more than two nodes (16 GPUs) (`ParameterServer.update(ranks=range(0, 16))`) out of the entire cluster.
+
+## Installation
+
+Use the fastest broadcast implementation
+
+```Bash
+pip install checkpoint-engine
+```
+
+Use the flexible P2P implementation, notice this will install `mooncake-transfer-engine` to support RDMA transfer between different ranks.
+
+```Bash
+pip install 'checkpoint-engine[p2p]'
+```
+
+If set `NCCL_IB_HCA` env, checkpoint-engine will use it to auto select net devices for different ranks. If not set, it will read all RDMA devices and try to divide them into each rank.
+
+## Getting Started
+
+Prepare an H800 or H20 machine with 8 GPUs with latest vLLM. Be sure to include [/collective_rpc API endpoint](https://github.com/vllm-project/vllm/commit/f7cf5b512ee41f36613deb2471a44de5f304f70d) commit (available in main branch) since checkpoint-engine will use this endpoint to update weights.
+
+```Bash
+cd /opt && git clone https://github.com/vllm-project/vllm && cd vllm
+uv venv --python 3.12 --seed
+source .venv/bin/activate
+VLLM_USE_PRECOMPILED=1 uv pip install --editable .
+```
+
+Install checkpoint-engine
+
+```Bash
+uv pip install 'checkpoint-engine[p2p]'
+```
+
+We use `Qwen/Qwen3-235B-A22B-Instruct-2507` (BF16) as the test model
+
+```Bash
+hf download Qwen/Qwen3-235B-A22B-Instruct-2507 --local-dir /opt/models/Qwen/Qwen3-235B-A22B-Instruct-2507/
+```
+
+Start vLLM in dev mode and set `--load-format dummy`. Notice that we also set `--worker-extension-cls=checkpoint_engine.worker.VllmColocateWorkerExtension`
+
+```Bash
+VLLM_SERVER_DEV_MODE=1 python3 -m vllm.entrypoints.openai.api_server --host 0.0.0.0 --port 19730 --trust-remote-code \
+    --tensor-parallel-size=8 --max-model-len 4096 --load-format dummy \
+    --served-model-name checkpoint-engine-demo --model /opt/models/Qwen/Qwen3-235B-A22B-Instruct-2507/ \
+    --worker-extension-cls checkpoint_engine.worker.VllmColocateWorkerExtension
+```
+
+Meanwhile, use this command to update weights by checkpoint-engine. No need to wait for vLLM to get ready.
+
+```Bash
+torchrun --nproc-per-node 8 examples/update.py --update-method all --checkpoint-path /opt/models/Qwen/Qwen3-235B-A22B-Instruct-2507/
+```
+
+### Reuse weights from existing instances
+
+New checkpoint-engine instances can join existing instances and reuse their weights. This is simple to achieve.
+
+First, start the existing instances with `--save-metas-file global_metas.pkl` to save global metas to a file and use `--sleep-time 300` to make sure they stay alive.
+
+```Bash
+torchrun --nproc-per-node 8 examples/update.py --checkpoint-path $MODEL_PATH \
+    --sleep-time 300 --save-metas-file global_metas.pkl
+```
+
+After a checkpoint is registered, new instances can obtain a copy of the checkpoint by setting `--load-metas-file global_metas.pkl`.
+
+```Bash
+torchrun --nproc-per-node 8 examples/update.py --load-metas-file global_metas.pkl
+```
+
+### FP8 quantization
+
+FP8 quantization currently do not natively work in vLLM when updating weights.
+We provide a simple patch in [`patches/vllm_fp8.patch`](./patches/vllm_fp8.patch) to handle the correct weight update.
+Notice this patch is only tested in DeepSeek-V3.1 and Kimi-K2. Other models may meet some compatible issues.
+
+A [PR](https://github.com/vllm-project/vllm/pull/24488) is opened to the vLLM project and waiting to discuss and review.
+
+### Test
+
+Run a simple correctness test for checkpoint_engine
+
+```bash
+torchrun --nproc-per-node 8 tests/test_update.py
+```
+
+## Limitations and Future Work
+
+- This project is currently only tested with vLLM. But it is easy to integrate with other frameworks like SGLang.
+- The perfect three-stage pipeline mentioned in our paper is currently not implemented. This could be useful for architectures where H2D and broadcast do not conflict in PCIE.
+- The P2P update method is currently not the optimal implementation since it will receive data only in rank 0 and broadcast to others synchronizely. This is a potential optimization in the future.
+
+## Acknowledgments
+
+This open source project uses the same vLLM interface in https://github.com/vllm-project/vllm/pull/24295 . Thanks for the comments and insights from [youkaichao](https://github.com/youkaichao).

checkpoint_engine-0.1.2/README.md

@@ -0,0 +1,152 @@
+# Checkpoint Engine
+Checkpoint-engine is a simple middleware to update model weights in LLM inference engines -- a critical step in reinforcement learning.
+We provide an efficient and lightweight implementation for inplace weight update:
+updating our [Kimi-K2](https://github.com/MoonshotAI/Kimi-K2) model (1 Trillion parameters) across thousands of GPUs takes about 20s.
+
+
+<div align="center">
+  <picture>
+      <img src="figures/checkpoint-engine.png" width="80%" alt="ckpt-engine">
+  </picture>
+</div>
+
+## Architecture
+
+The core weight update logic is in `ParameterServer` class, a service colocated with inference engines. It provides two implementations of weight update: Broadcast and P2P.
+
+- **Broadcast**: Used when a large number of inference instances need to update weights in synchronous. This is the fastest implementation and should be used as the default update method. See `_update_per_bucket`.
+- **P2P**: Used when new inference instances are dynamically added (due to restarts or dynamic availability) while the existing instances are already serving requests. Under this scenario, to avoid affecting the workloads on existing instances, we use the [`mooncake-transfer-engine`](https://github.com/kvcache-ai/Mooncake?tab=readme-ov-file#use-python-package) to P2P send weights from CPUs in existing instances to GPUs in new instances. See `_update_per_bucket_p2p`.
+
+### Optimized Weight Broadcast
+In the *Broadcast* implementation, the checkpoint-engine holds references to sharded weights in CPU memory, and need to efficiently broadcast them to a cluster of inference instances, often under a different sharding pattern.
+We arrange the data transfer into 3 stages:
+1. H2D: moving weights to GPU memory. These weights may come from disk or the training engine.
+2. broadcast: broadcast among checkpoint engine workers; the data results in a CUDA IPC buffer shared with inference engine.
+3. reload: inference engine decides what subset of weights to copy from the broadcasted data.
+
+Checkpoint-engine orchestrates the entire transfer process. It first gathers necessary metadata to create a plan, including deciding the proper bucket size for data transfer.
+It then executes the transfer, where it controls the inference engine through a ZeroMQ socket. To maximize performance, it organizes the data transfers into a pipeline with overlapped communication and copy, illustrated below. The details can be found in [Kimi-K2 Technical Report](https://arxiv.org/abs/2507.20534).
+
+
+<div align="center">
+  <picture>
+      <img src="figures/pipeline.png" width="80%" alt="pipeline">
+  </picture>
+</div>
+
+Pipelining naturally requires more GPU memory. When memory is not enough, checkpoint-engine will fallback to serial execution.
+
+## Benchmark
+
+| Model                                | Device Info  | GatherMetas | Update (Broadcast) | Update (P2P)            |
+| :----------------------------------- | :----------- | :---------- |:-------------------| :---------------------- |
+| GLM-4.5-Air (BF16)                   | 8xH800 TP8  | 0.17s       | 3.94s (1.42GiB)    | 8.83s (4.77GiB)         |
+| Qwen3-235B-A22B-Instruct-2507 (BF16) | 8xH800 TP8  | 0.46s       | 6.75s (2.69GiB)    | 16.47s (4.05GiB)        |
+| DeepSeek-V3.1 (FP8)                  | 16xH20 TP16  | 1.44s       | 12.22s (2.38GiB)   | 25.77s (3.61GiB)        |
+| Kimi-K2-Instruct (FP8)               | 16xH20 TP16  | 1.81s       | 15.45s (2.93GiB)   | 36.24s (4.46GiB)        |
+| DeepSeek-V3.1 (FP8)                  | 256xH20 TP16 | 1.40s       | 13.88s (2.54GiB)   | 33.30s (3.86 GiB) |
+| Kimi-K2-Instruct (FP8)               | 256xH20 TP16 | 1.88s       | 21.50s (2.99GiB)   | 34.49s (4.57 GiB) |
+
+All results above are tested by [`examples/update.py`](./examples/update.py) and use [vLLM v0.10.2rc1](https://github.com/vllm-project/vllm/tree/v0.10.2rc1) as inference engine. Some notes:
+
+* FP8 test needs additional vLLM patches, see [FP8 quantization](#fp8-quantization).
+* Device Info: we tested various combination of devices and parallelism setups. For example, a 256-GPU TP16 setup means that we deploy 16 vLLM instances, each with 16-way tensor parallelism.
+* Since update duration is related to IPC bucket size, we provide the bucket size in the table.
+* The P2P time were tested for updating no more than two nodes (16 GPUs) (`ParameterServer.update(ranks=range(0, 16))`) out of the entire cluster.
+
+## Installation
+
+Use the fastest broadcast implementation
+
+```Bash
+pip install checkpoint-engine
+```
+
+Use the flexible P2P implementation, notice this will install `mooncake-transfer-engine` to support RDMA transfer between different ranks.
+
+```Bash
+pip install 'checkpoint-engine[p2p]'
+```
+
+If set `NCCL_IB_HCA` env, checkpoint-engine will use it to auto select net devices for different ranks. If not set, it will read all RDMA devices and try to divide them into each rank.
+
+## Getting Started
+
+Prepare an H800 or H20 machine with 8 GPUs with latest vLLM. Be sure to include [/collective_rpc API endpoint](https://github.com/vllm-project/vllm/commit/f7cf5b512ee41f36613deb2471a44de5f304f70d) commit (available in main branch) since checkpoint-engine will use this endpoint to update weights.
+
+```Bash
+cd /opt && git clone https://github.com/vllm-project/vllm && cd vllm
+uv venv --python 3.12 --seed
+source .venv/bin/activate
+VLLM_USE_PRECOMPILED=1 uv pip install --editable .
+```
+
+Install checkpoint-engine
+
+```Bash
+uv pip install 'checkpoint-engine[p2p]'
+```
+
+We use `Qwen/Qwen3-235B-A22B-Instruct-2507` (BF16) as the test model
+
+```Bash
+hf download Qwen/Qwen3-235B-A22B-Instruct-2507 --local-dir /opt/models/Qwen/Qwen3-235B-A22B-Instruct-2507/
+```
+
+Start vLLM in dev mode and set `--load-format dummy`. Notice that we also set `--worker-extension-cls=checkpoint_engine.worker.VllmColocateWorkerExtension`
+
+```Bash
+VLLM_SERVER_DEV_MODE=1 python3 -m vllm.entrypoints.openai.api_server --host 0.0.0.0 --port 19730 --trust-remote-code \
+    --tensor-parallel-size=8 --max-model-len 4096 --load-format dummy \
+    --served-model-name checkpoint-engine-demo --model /opt/models/Qwen/Qwen3-235B-A22B-Instruct-2507/ \
+    --worker-extension-cls checkpoint_engine.worker.VllmColocateWorkerExtension
+```
+
+Meanwhile, use this command to update weights by checkpoint-engine. No need to wait for vLLM to get ready.
+
+```Bash
+torchrun --nproc-per-node 8 examples/update.py --update-method all --checkpoint-path /opt/models/Qwen/Qwen3-235B-A22B-Instruct-2507/
+```
+
+### Reuse weights from existing instances
+
+New checkpoint-engine instances can join existing instances and reuse their weights. This is simple to achieve.
+
+First, start the existing instances with `--save-metas-file global_metas.pkl` to save global metas to a file and use `--sleep-time 300` to make sure they stay alive.
+
+```Bash
+torchrun --nproc-per-node 8 examples/update.py --checkpoint-path $MODEL_PATH \
+    --sleep-time 300 --save-metas-file global_metas.pkl
+```
+
+After a checkpoint is registered, new instances can obtain a copy of the checkpoint by setting `--load-metas-file global_metas.pkl`.
+
+```Bash
+torchrun --nproc-per-node 8 examples/update.py --load-metas-file global_metas.pkl
+```
+
+### FP8 quantization
+
+FP8 quantization currently do not natively work in vLLM when updating weights.
+We provide a simple patch in [`patches/vllm_fp8.patch`](./patches/vllm_fp8.patch) to handle the correct weight update.
+Notice this patch is only tested in DeepSeek-V3.1 and Kimi-K2. Other models may meet some compatible issues.
+
+A [PR](https://github.com/vllm-project/vllm/pull/24488) is opened to the vLLM project and waiting to discuss and review.
+
+### Test
+
+Run a simple correctness test for checkpoint_engine
+
+```bash
+torchrun --nproc-per-node 8 tests/test_update.py
+```
+
+## Limitations and Future Work
+
+- This project is currently only tested with vLLM. But it is easy to integrate with other frameworks like SGLang.
+- The perfect three-stage pipeline mentioned in our paper is currently not implemented. This could be useful for architectures where H2D and broadcast do not conflict in PCIE.
+- The P2P update method is currently not the optimal implementation since it will receive data only in rank 0 and broadcast to others synchronizely. This is a potential optimization in the future.
+
+## Acknowledgments
+
+This open source project uses the same vLLM interface in https://github.com/vllm-project/vllm/pull/24295 . Thanks for the comments and insights from [youkaichao](https://github.com/youkaichao).

checkpoint_engine-0.1.2/checkpoint_engine/__init__.py

@@ -0,0 +1,4 @@
+try:
+    from ._version import __version__
+except ImportError:
+    __version__ = "dev"

checkpoint_engine-0.1.2/checkpoint_engine/_version.py

@@ -0,0 +1,34 @@
+# file generated by setuptools-scm
+# don't change, don't track in version control
+
+__all__ = [
+    "__version__",
+    "__version_tuple__",
+    "version",
+    "version_tuple",
+    "__commit_id__",
+    "commit_id",
+]
+
+TYPE_CHECKING = False
+if TYPE_CHECKING:
+    from typing import Tuple
+    from typing import Union
+
+    VERSION_TUPLE = Tuple[Union[int, str], ...]
+    COMMIT_ID = Union[str, None]
+else:
+    VERSION_TUPLE = object
+    COMMIT_ID = object
+
+version: str
+__version__: str
+__version_tuple__: VERSION_TUPLE
+version_tuple: VERSION_TUPLE
+commit_id: COMMIT_ID
+__commit_id__: COMMIT_ID
+
+__version__ = version = '0.1.2'
+__version_tuple__ = version_tuple = (0, 1, 2)
+
+__commit_id__ = commit_id = 'g716c0dad9'