tigrbl-canon
Deprecated legacy compatibility package for Tigrbl canonical mapping, router binding, schema attachment, RPC and REST exposure, and column inference utilities.
What is tigrbl-canon?
Deprecated legacy compatibility package for Tigrbl canonical mapping, router binding, schema attachment, RPC and REST exposure, and column inference utilities. New code should not add this package; it exists only to carry older tigrbl_canon import paths during migrations.
Why use tigrbl-canon?
Use it only when maintaining older integrations that still import the historical canonical package boundary. Do not use it for new Tigrbl applications or extensions.
When should I install tigrbl-canon?
Install it only for compatibility migrations that still require tigrbl_canon imports. Prefer the current split packages for new work.
Who is tigrbl-canon for?
Maintainers carrying legacy Tigrbl integrations forward.
Where does tigrbl-canon fit?
tigrbl-canon lives at pkgs/99_deprecated/tigrbl_canon and serves legacy compatibility while migrating to current split packages. It is not part of the active facade dependency path.
How does tigrbl-canon work?
It depends on current split packages and keeps historical import paths available while newer package boundaries own active behavior. It must not depend on the tigrbl facade package.
Install
uv add tigrbl-canon
pip install tigrbl-canon
Surface Coverage
| Surface | Value |
|---|---|
| PyPI package | tigrbl-canon |
| Repository path | pkgs/99_deprecated/tigrbl_canon |
| Python import root | tigrbl_canon |
| Console scripts | none declared |
| Entry points | none declared |
| Optional extras | none declared |
| Legal files | LICENSE, NOTICE |
| Supported Python | `3.10 |
What It Owns
tigrbl-canon owns the deprecated legacy compatibility package boundary. It should be installed only when an older integration still needs the historical tigrbl_canon import root during migration.
Implementation orientation:
tigrbl_canon: column/, mapping/
Public API and Import Surface
- Import roots:
tigrbl_canon. - Public symbols:
_DEPRECATION_MESSAGE. - Workspace dependencies:
tigrbl-ops-oltp,tigrbl-base,tigrbl-core,tigrbl-runtime,tigrbl-atoms. - External runtime dependencies: none declared.
Usage Examples
Verify the installed package
python -m pip show tigrbl-canon
python - <<'PY'
from importlib.metadata import version
print(version("tigrbl-canon"))
PY
Import the compatibility boundary
import tigrbl_canon
print(tigrbl_canon.__name__)
Prefer current split packages for new code
uv add tigrbl-core tigrbl-base tigrbl-runtime
Audit remaining legacy imports
rg "tigrbl_canon|tigrbl-canon" .
How To Choose This Package
Choose tigrbl-canon only when an existing integration still imports tigrbl_canon and cannot migrate immediately. Choose lower-level packages such as tigrbl-core, tigrbl-base, or tigrbl-runtime when building framework extensions or testing a specific internal boundary.
Related Packages
Documentation Links
- Workspace docs
- Package catalog
- Package layout
- Current target
- Current state
- SSOT registry
- Release workflow
Support
- Community: Discord.
- Issues: GitHub Issues.
- Repository: pkgs/99_deprecated/tigrbl_canon.
Package-local Boundary
This README is the package-local distribution entry point for tigrbl-canon. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.
Certification Status
- Package status: deprecated, inactive compatibility package in the
tigrbl/tigrblworkspace. - Governance source: SSOT registry.
- Release evidence: publish workflow validates package builds, tests, GitHub release assets, and PyPI publication for managed packages.
- Local certification guard:
pkgs/97_tests/tigrbl_tests/tests/unit/test_package_badges_and_notices.pyverifies every package README keeps the Discord badge, Apache 2.0 badge, explicit Python-version badge,LICENSE, andNOTICE. - Scope note: this README documents the package boundary. Runtime feature support remains governed by
.ssot/entities and the conformance docs linked below.
License
Licensed under the Apache License, Version 2.0. See LICENSE, NOTICE, and the official Apache 2.0 license text.
Metadata
Release files for tigrbl-canon 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_canon-0.4.5.tar.gz | 64.9 kB | Without provenance | Details for tigrbl_canon-0.4.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tigrbl_canon-0.4.5-py3-none-any.whl | Python 3 | none | any | Details for tigrbl_canon-0.4.5-py3-none-any.whl |
Total release size: 155.5 kB
Release files / tigrbl_canon-0.4.5.tar.gz
| Download URL | tigrbl_canon-0.4.5.tar.gz |
|---|---|
| Size | 64.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4c5c72ccd92e23701cc004214048e6ee0872b5e1ecb31d6075a7e6bb00dbd2a0
|
|
BLAKE2b-256 checksum How to use checksums |
999875c9beda18f5636a6b25c10c8625a782155f469e53b53870c6c7a3e32378
|
| 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_canon-0.4.5-py3-none-any.whl
| Download URL | tigrbl_canon-0.4.5-py3-none-any.whl |
|---|---|
| Size | 90.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1e2cf20f43511cb03def593f09b1f159f7772558f5d28d787fa4f35ad600d608
|
|
BLAKE2b-256 checksum How to use checksums |
adb1f03596ab054650963d4ae5b0972db75cfa2821d220bce652e61dbe0daac1
|
| 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-canon 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.