tigrbl-canon 0.4.5.dev4

Deprecated legacy compatibility package for Tigrbl canonical mapping, router binding, schema attachment, RPC and REST exposure, and column inference utilities.

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/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/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

• tigrbl-ops-oltp
• tigrbl-base
• tigrbl-core
• tigrbl-runtime
• tigrbl-atoms

Documentation Links

• Workspace docs
• Package catalog
• Package layout
• Current target
• Current state
• SSOT registry
• Release workflow

Support

• Community: Discord.
• Issues: GitHub Issues.
• Repository: pkgs/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/tigrbl workspace.
• 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/core/tigrbl_tests/tests/unit/test_package_badges_and_notices.py verifies every package README keeps the Discord badge, Apache 2.0 badge, explicit Python-version badge, LICENSE, and NOTICE.
• 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.