tigrcorn-core

Typed core primitives, errors, constants, and utilities shared by the Tigrcorn ASGI3 Python web server packages.

Install

uv add tigrcorn-core

pip install tigrcorn-core

Use the aggregate tigrcorn distribution when you want the full ASGI3 Python web server stack. Install tigrcorn-core directly when you want only this package boundary and its declared dependencies.

What It Owns

tigrcorn-core owns constants, errors, types, and utils primitives. Its import package is tigrcorn_core, and its declared package dependencies are: none.

This package page is written for developers searching for Tigrcorn ASGI3 server components, Python web server packages, HTTP/3 and QUIC support, WebSocket and WebTransport-adjacent surfaces, and Apache 2.0 licensed infrastructure.

Why Use This?

Use tigrcorn-core when you want the core layer as a direct install target instead of the full server bundle. It lets application, operator, or certification workflows depend on this boundary explicitly while keeping the broader Tigrcorn runtime assembled from smaller repo-owned package surfaces.

FAQ

What does this package export?

The package exports through the tigrcorn_core namespace and keeps the root tigrcorn package as the compatibility umbrella.

Which boundary does this package own?

It is the package boundary for constants, errors, types, and utils primitives in the Tigrcorn package graph.

What does this package intentionally avoid?

It stays dependency-light and infrastructure-neutral so every higher Tigrcorn package can reuse shared constants, types, and core errors without pulling in HTTP, TLS, protocol, or runtime stacks.

Features

• Owns constants, errors, types, and utils primitives inside the Tigrcorn split-package architecture.
• Publishes the tigrcorn_core import surface for named public helpers and entrypoints.
• Declared runtime dependencies: none.
• Optional dependency surface: none.
• Supports Python 3.10, 3.11, 3.12, 3.13, and 3.14.

Use It When

Use tigrcorn-core when you need core-level behavior without pulling the entire server stack into the import surface. It is part of Tigrcorn's split-package architecture, so it can be installed independently while remaining linked to the rest of the Tigrcorn package family on PyPI.

Import Surface

import tigrcorn_core

print(tigrcorn_core.DEFAULT_HOST)
print(tigrcorn_core.DEFAULT_PORT)

The package exposes its supported public surface through the tigrcorn_core namespace. The root tigrcorn package keeps compatibility shims for users who install the full server distribution.

Related Packages

• tigrcorn
• tigrcorn-config
• tigrcorn-http
• tigrcorn-asgi

Package Graph

tigrcorn-core | tigrcorn-config | tigrcorn-http | tigrcorn-asgi | tigrcorn-contract | tigrcorn-transports | tigrcorn-security | tigrcorn-protocols | tigrcorn-static | tigrcorn-observability | tigrcorn-runtime | tigrcorn-compat | tigrcorn-certification

Best Practices

• Keep this package at the bottom of new dependency chains.
• Import protocol, runtime, or security behavior from higher packages instead of backfilling it here.
• Use the exported constants and error types instead of cloning parallel primitives in downstream packages.

License

Apache-2.0