What is tigrbl_engine_rom?
tigrbl_engine_rom loads one mapping-backed row image and serves it through Tigrbl's engine-session contract. The engine configuration is bound as an input to a table.
Why use tigrbl_engine_rom?
Use it for embedded catalogs, fixtures, policy data, reference tables, and other datasets that must never change at runtime.
When should I install tigrbl_engine_rom?
Install it when your application needs fast reads from a fixed memory image and should fail closed on every write.
Who is tigrbl_engine_rom for?
It is for application developers shipping trusted reference data or deterministic read-only test images.
Where does tigrbl_engine_rom fit?
It is a standalone package under pkgs/90_engines and is discovered through the tigrbl.engine entry-point group as kind rom.
How does tigrbl_engine_rom work?
ROMEngine subclasses Tigrbl's EngineBase. Construction validates the bound table's rows and primary key, deeply detaches the source data, and freezes it. Reads always return caller-owned copies. Sessions force read_only=True, even if a caller requests otherwise.
Install
uv add tigrbl_engine_rom
Surface Coverage
| Surface | Value |
|---|---|
| Engine kind | rom |
| Python import | tigrbl_engine_rom |
| Entry point | tigrbl.engine |
| Persistence | process-local immutable memory |
| Supported Python | `3.10 |
What It Owns
The package owns the ROM image, read-only session, plugin registration, and scalar result facade.
Public API and Import Surface
Public symbols are ROMEngine, ROMSession, ROMResult, build_rom, capabilities, and register.
Usage Examples
from tigrbl_engine_rom import build_rom
engine, sessionmaker = build_rom(mapping={
"rows": [
{"code": "US", "name": "United States"},
{"code": "CA", "name": "Canada"},
],
"primary_key": "code",
})
session = sessionmaker()
assert session.get_row("CA")["name"] == "Canada"
Bind the engine configuration into a table:
from tigrbl.factories.table import defineTableSpec
class CountrySpec(defineTableSpec(engine={
"kind": "rom",
"rows": [
{"code": "US", "name": "United States"},
{"code": "CA", "name": "Canada"},
],
"primary_key": "code",
})):
pass
How To Choose This Package
Choose ROM for immutable embedded data. Choose tigrbl_engine_inmemory when transactions and runtime writes are required.
Related Packages
tigrbltigrbl_engine_inmemorytigrbl_engine_memkv
Documentation Links
Support
Certification Status
The package is implemented with package-local behavioral tests. Certification remains governed by the repository SSOT registry and release workflows.
License
Licensed under the Apache License, Version 2.0. See LICENSE and NOTICE.
Workspace documentation
This README is the package-local distribution entry point. See workspace documentation, current conformance target, package catalog, package layout, and SSOT registry.
Metadata
Release files for tigrbl_engine_rom 0.4.5
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 |
|---|---|---|---|---|
| tigrbl_engine_rom-0.4.5.tar.gz | 9.2 kB | Without provenance | Details for tigrbl_engine_rom-0.4.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tigrbl_engine_rom-0.4.5-py3-none-any.whl | Python 3 | none | any | Details for tigrbl_engine_rom-0.4.5-py3-none-any.whl |
Total release size: 18.8 kB
Release files / tigrbl_engine_rom-0.4.5.tar.gz
| Download URL | tigrbl_engine_rom-0.4.5.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
faac91b93a7016b1c5df9f0ab56a6793b1846a4399e289efe893e17e45b6a68a
|
|
BLAKE2b-256 checksum How to use checksums |
aa215a42df039f710fca5b47029d06ab258e0f19ce43b57b19412b1d77f46051
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tigrbl_engine_rom-0.4.5-py3-none-any.whl
| Download URL | tigrbl_engine_rom-0.4.5-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2fae2a7ff85e201e317092ca37ce3285cbeeeaccef7531ae120dff957975f386
|
|
BLAKE2b-256 checksum How to use checksums |
217a61c1b39aa2119191f1d68664916ca0244474bae3d0a649eaa45eab8b20d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tigrbl_engine_rom 0.4.5
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.