This release is a pre-release and may not be stable for production use.
LMCache InProcess
lmcache_inprocess packages LMCache's legacy in-process engine separately from
the main LMCache distribution. It keeps the
existing Python import path, lmcache.inprocess, so current vLLM, TensorRT-LLM,
configuration, and plugin integrations do not need an API rename.
The wheel also supplies
lmcache.integration.vllm.vllm_v1_adapter as a compatibility re-export because
vLLM's connector imports that canonical path. The implementation remains under
lmcache.inprocess.integration.vllm.
The initial source snapshot is copied from LMCache dev commit
95ced2b137e3d854de662a45dd3c6ca3fee0753b.
The exact source revision is also recorded in UPSTREAM_REVISION.
Install
Install a compatible LMCache build first, then this package:
python -m pip install 'lmcache>=0.5.7rc3'
python -m pip install lmcache_inprocess
For development against LMCache dev:
NO_GPU_EXT=1 python -m pip install \
'lmcache @ git+https://github.com/LMCache/LMCache.git@dev'
python -m pip install -e . --no-deps
The distribution is pure Python. Native extensions remain owned and shipped by
the lmcache dependency. A CLI-only NO_NATIVE_EXT=1 LMCache installation is
not sufficient because the in-process engine requires LMCache's common native
operations; CPU validation uses NO_GPU_EXT=1.
Compatibility contract
- Distribution name:
lmcache_inprocess - Import namespace:
lmcache.inprocess - Base dependency:
lmcache>=0.5.7rc3 - Python: 3.10 through 3.14
- Supported source of shared native extensions: the installed
lmcachepackage
Because both distributions contribute files below the top-level lmcache
directory, install and uninstall them with the same environment manager. A
future LMCache release should stop shipping lmcache/inprocess before both
packages are published as stable releases, avoiding overlapping wheel ownership.
Development and validation
python -m pip install -r requirements/test.txt
python -m build
python -m twine check dist/*
python -m pytest -q tests/smoke
python -m pytest -q tests/inprocess/v1/test_mock_gpu_connector.py
CI builds and installs the wheel in a clean environment, runs CPU smoke tests,
and tests compatibility against a pinned LMCache revision and current LMCache
dev. GPU end-to-end validation is available through the manual workflow in
.github/workflows/gpu-e2e.yml on a repository runner labeled
self-hosted, linux, x64, gpu, and h200.
Repository layout
lmcache/inprocess/: package sourcetests/inprocess/: copied unit and integration testsexamples/inprocess/: in-process examplesbenchmarks/inprocess/: in-process benchmarksscripts/sync_from_lmcache.sh: reproducible upstream refresh helper
Release
Create a GitHub release with a vX.Y.Z tag. The release workflow builds the
source distribution and universal wheel, validates both, uploads them as GitHub
release artifacts, and publishes to PyPI through Trusted Publishing when the
pypi environment is configured for this repository.
Metadata
Release files for lmcache-inprocess 0.1.0rc2
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 |
|---|---|---|---|---|
| lmcache_inprocess-0.1.0rc2.tar.gz | 954.2 kB | With provenance | Details for lmcache_inprocess-0.1.0rc2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lmcache_inprocess-0.1.0rc2-py3-none-any.whl | Python 3 | none | any | Details for lmcache_inprocess-0.1.0rc2-py3-none-any.whl |
Total release size: 1.6 MB
Release files / lmcache_inprocess-0.1.0rc2.tar.gz
| Download URL | lmcache_inprocess-0.1.0rc2.tar.gz |
|---|---|
| Size | 954.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18d1d487d94e45c3fe32ae850a6d2224597b1dd9fa8c53c61facf1a4e8d43dad
|
|
BLAKE2b-256 checksum How to use checksums |
f0096f596f4cb84be0a3c297e2ee6ac5cb3df25d95c0f805c317ee495a155e09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Nov 3, 2026.
Transparency logRelease files / lmcache_inprocess-0.1.0rc2-py3-none-any.whl
| Download URL | lmcache_inprocess-0.1.0rc2-py3-none-any.whl |
|---|---|
| Size | 674.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a2b117387bc57cc59d4165b352c95109b2a26bb40471043231434c1ef6687ba
|
|
BLAKE2b-256 checksum How to use checksums |
d3b5840f7f5628a61a5453439fdea07fa4bdd5e952c2ade548797fdba4cecd91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Nov 3, 2026.
Transparency logSecurity for lmcache-inprocess 0.1.0rc2
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 lmcache_inprocess-0.1.0rc2.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 Nov 3, 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.