tigrcorn-runtime 0.3.16.dev13

Server runner, app loading, lifecycle hooks, workers, reload, and embedded runtime for the Tigrcorn ASGI3 web server.

tigrcorn-runtime

Server runner, app loading, lifecycle hooks, workers, reload, and embedded runtime for the Tigrcorn ASGI3 web server.

Install

uv add tigrcorn-runtime

pip install tigrcorn-runtime

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

What It Owns

tigrcorn-runtime owns server runner, app loading, bootstrap, signals, shutdown, workers, embedding, and cli. Its import package is tigrcorn_runtime, and its declared package dependencies are: tigrcorn-core, tigrcorn-config, tigrcorn-asgi, tigrcorn-transports, tigrcorn-protocols, tigrcorn-security.

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

Which boundary does this package own?

It is the package boundary for server runner, app loading, bootstrap, signals, shutdown, workers, embedding, and cli in the Tigrcorn package graph.

What should be imported from the runtime package first?

Start with run, serve, or serve_import_string when you need the packaged server entrypoints, embedded runtime orchestration, bootstrap flow, or worker lifecycle management.

Features

• Owns server runner, app loading, bootstrap, signals, shutdown, workers, embedding, and cli inside the Tigrcorn split-package architecture.
• Publishes the tigrcorn_runtime import surface for named public helpers and entrypoints.
• Declared runtime dependencies: tigrcorn-core, tigrcorn-config, tigrcorn-asgi, tigrcorn-transports, tigrcorn-protocols, tigrcorn-security.
• Optional dependency surface: uvloop, trio.
• Supports Python 3.10, 3.11, 3.12, 3.13, and 3.14.

Use It When

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

from tigrcorn_runtime import run

print(run.__name__)

Namespace discovery starts with import tigrcorn_runtime.

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

Related Packages

• tigrcorn-core
• tigrcorn-config
• tigrcorn-asgi
• tigrcorn-transports
• tigrcorn-protocols
• tigrcorn-security
• tigrcorn
• tigrcorn-compat

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

• Use this package when you need the packaged server entrypoints or embedded runtime orchestration.
• Keep worker, reload, and bootstrap behavior documented here before surfacing it at the repo root.
• Use config, protocol, transport, and security packages as inputs instead of re-owning those concerns in runtime code.

License

Apache-2.0