tigrcorn-asgi

ASGI3 scope, event, receive/send, and extension primitives for the Tigrcorn Python web server.

Install

uv add tigrcorn-asgi

pip install tigrcorn-asgi

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

What It Owns

tigrcorn-asgi owns ASGI scopes, ASGI events, receive/send channels, extensions, and connection state. Its import package is tigrcorn_asgi, and its declared package dependencies are: tigrcorn-core.

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-asgi when you want the asgi 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_asgi namespace and keeps the root tigrcorn package as the compatibility umbrella.

Which boundary does this package own?

It is the package boundary for ASGI scopes, ASGI events, receive/send channels, extensions, and connection state in the Tigrcorn package graph.

Why is this package separate from runtime and protocols?

It isolates scopes, events, extensions, and receive/send contracts so protocol and runtime packages can share one ASGI3 boundary without duplicating event or scope logic.

Features

• Owns ASGI scopes, ASGI events, receive/send channels, extensions, and connection state inside the Tigrcorn split-package architecture.
• Publishes the tigrcorn_asgi import surface for module-oriented public surfaces.
• Declared runtime dependencies: tigrcorn-core.
• Optional dependency surface: none.
• Supports Python 3.10, 3.11, 3.12, 3.13, and 3.14.

Use It When

Use tigrcorn-asgi when you need asgi-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_asgi

print(tigrcorn_asgi.__name__)

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

Related Packages

• tigrcorn-core
• tigrcorn

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 new event and scope behavior aligned to ASGI3 contracts first, then layer protocol-specific behavior on top.
• Reuse the shared ASGI surface here before inventing protocol-local scope or event shapes.
• Validate extension and connection-state assumptions at this boundary before they leak into runtime code.

License

Apache-2.0