nessie-backend-conformance
The substrate-agnostic conformance suite every nessie-store backend must pass — and the inside extension point: write a storage backend in Python and validate it against the exact same suites a Rust backend passes.
Install
pip install nessie-backend-conformance # Python
cargo add nessie-backend-conformance # Rust (dev-dependency)
Usage (Python) — validate a Python-authored backend
from nessie_backend_conformance import run_all, ConformanceError
class MyBackend:
def capabilities(self): return {"snapshots": True, "clones": True, "replication": False}
def create_volume(self, name, size_bytes): ...
def get_volume(self, uuid): ... # return None when absent
# … list_volumes / delete_volume / patch_volume / access_handle
# … create_snapshot / list_snapshots / get_snapshot / delete_snapshot / create_clone
run_all(MyBackend()) # raises ConformanceError on the first violation
Methods exchange plain domain-shaped dicts ({uuid, name, state, style, vol_type, size_bytes?, clone?} for volumes). A Rust adapter wraps the Python
object and runs the suites by calling back into Python under the GIL. See
examples/python_backend.py for a complete
reference backend.
Usage (Rust)
nessie_backend_conformance::run_all(&my_backend); // panics on the first violation
Dual-licensed MIT OR Apache-2.0.
Metadata
Release files for nessie-backend-conformance 0.4.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 2.1 MB
Release files / nessie_backend_conformance-0.4.3-cp310-abi3-win_amd64.whl
| Download URL | nessie_backend_conformance-0.4.3-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 321.1 kB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
67cc6261fc525fe300a6e4282c0b999a07e66de947af1d5f9b484eccdab4a6c3
|
|
BLAKE2b-256 checksum How to use checksums |
8161eaabeea7a8615ddba43dcb0bfb542c4d7bdeab1b9b38261d136313251df1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / nessie_backend_conformance-0.4.3-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | nessie_backend_conformance-0.4.3-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 452.5 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
87462b57a4b357e6d3951687c1d0053672f917ba9a661c41e8a0497ed64145f8
|
|
BLAKE2b-256 checksum How to use checksums |
53fbd4fc1033ca325254e2cc7f66c9c6241b00625911ba9e7b34c12e47fb3c9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / nessie_backend_conformance-0.4.3-cp310-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | nessie_backend_conformance-0.4.3-cp310-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 451.2 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
4b848017036a164358928c1369c74f3e7e4a1119f8108531c67abd96b3b68b54
|
|
BLAKE2b-256 checksum How to use checksums |
9b56eebbcfd4eddd2a8155fe78bc4299f4584179ef02cc3869e875b9f95b9459
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / nessie_backend_conformance-0.4.3-cp310-abi3-macosx_10_12_universal2.macosx_10_12_x86_64.macosx_11_0_arm64.whl
| Download URL | nessie_backend_conformance-0.4.3-cp310-abi3-macosx_10_12_universal2.macosx_10_12_x86_64.macosx_11_0_arm64.whl |
|---|---|
| Size | 831.4 kB |
| Tags | CPython 3.10 abi3 macOS 10.12+ universal2 (ARM64, x86-64) macOS 10.12+ x86-64 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0113ec09d49052104aa5c9e87be3787cc5401c267c405d8d960c5a3ed44b298b
|
|
BLAKE2b-256 checksum How to use checksums |
7666a50e9519496c61ae0cf075ec50476164b1eaa5e91239375f74dd85fe0ea1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for nessie-backend-conformance 0.4.3
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.