xtr-http-kernel 4.0.4__tar.gz → 4.1.0__tar.gz

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: xtr-http-kernel
-Version: 4.0.4
+Version: 4.1.0
 Summary: Requests turned into responses through events: a request lifecycle for FastAPI applications on the xtr kernel.
 Keywords: http,kernel,request,lifecycle,events,middleware,fastapi
 Author: Xterr
@@ -16,7 +16,7 @@ Classifier: Programming Language :: Python :: 3.14
 Classifier: Typing :: Typed
 Requires-Dist: fastapi>=0.121.3
 Requires-Dist: starlette>=0.40
-Requires-Dist: xtr-dependency-injection[fastapi]>=4.0,<5
+Requires-Dist: xtr-dependency-injection>=4.0,<5
 Requires-Dist: xtr-event-dispatcher>=4.0,<5
 Requires-Dist: xtr-event-dispatcher-contracts>=4.0,<5
 Requires-Dist: xtr-http-message>=4.0,<5
@@ -25,14 +25,7 @@ Requires-Dist: xtr-logging-contracts>=4.0,<5
 Requires-Dist: xtr-service-contracts>=4.0,<5
 Requires-Dist: typing-extensions>=4.4
 Requires-Dist: python-multipart>=0.0.18
-Requires-Dist: xtr-console>=4.0,<5 ; extra == 'console'
-Requires-Dist: xtr-logging>=4.0,<5 ; extra == 'logging'
-Requires-Dist: xtr-clock>=4.0,<5 ; extra == 'rate-limiter'
-Requires-Dist: xtr-rate-limiter[di]>=4.0,<5 ; extra == 'rate-limiter'
 Requires-Python: >=3.11
-Provides-Extra: console
-Provides-Extra: logging
-Provides-Extra: rate-limiter
 Description-Content-Type: text/markdown
 
 <div align="center">
@@ -75,16 +68,17 @@ Listeners are services, so they come from the container with everything else the
 ## Install
 
 ```sh
-uv add xtr-http-kernel                      # the lifecycle, its bundle and setup
-uv add "xtr-http-kernel[logging]"           # + the listeners that log
-uv add "xtr-http-kernel[console]"           # + the commands that report on the router
-uv add "xtr-http-kernel[rate-limiter]"      # + rate limits on routes, routers and the app
+uv add xtr-http-kernel     # the lifecycle, its bundle and setup
+uv add xtr-logging         # beside it: the listeners that log
+uv add xtr-console         # beside it: the commands that report on the router
+uv add xtr-rate-limiter    # beside it: rate limits on routes, routers and the app
 ```
 
 Requires Python 3.11+. The web framework and the container layer come with the package
-itself — this *is* the integration — so neither is an extra, and neither is the
-[HTTP message contract](../xtr-http-message-contracts) or
-[its implementation](../xtr-http-message): the bridge below is made of them.
+itself — this *is* the integration — and so do the
+[HTTP message contract](../xtr-http-message-contracts) and
+[its implementation](../xtr-http-message): the bridge below is made of them. The three
+packages beside it are optional: each is used when it is installed and left alone when not.
 
 ## Quick start
 
@@ -375,9 +369,10 @@ id. The request id settles right after the unit opens, for the same reason.
 
 ## Rate limits
 
-With the `rate-limiter` extra, a route, a router or the whole application can be held to a
-limiter configured in [xtr-rate-limiter](../xtr-rate-limiter)'s bundle. `RateLimited` is one
-declaration, written as a decorator or wherever the framework takes a dependency:
+With [xtr-rate-limiter](../xtr-rate-limiter) installed beside this package, a route, a router or
+the whole application can be held to a limiter configured in that package's bundle.
+`RateLimited` is one declaration, written as a decorator or wherever the framework takes a
+dependency:
 
 ```python
 from fastapi import APIRouter, FastAPI, Request
@@ -454,11 +449,12 @@ Everything adding this package to an application on
 [xtr-dependency-injection](../xtr-dependency-injection) takes — and, read backwards, what
 removing it undoes.
 
-- **Install** — `uv add "xtr-http-kernel[logging,console]"`; `logging` brings the listeners
-  that write to a log, `console` the commands that report on the router, `rate-limiter` the
-  [rate limits](#rate-limits). None is needed to serve requests. The
+- **Install** — `uv add xtr-http-kernel`; install [xtr-logging](../xtr-logging) beside it for
+  the listeners that write to a log, [xtr-console](../xtr-console) for the commands that report
+  on the router, [xtr-rate-limiter](../xtr-rate-limiter) for the [rate limits](#rate-limits).
+  None is needed to serve requests. The
   [HTTP message contract](../xtr-http-message-contracts) and
-  [its implementation](../xtr-http-message) come with the package, not behind an extra: the
+  [its implementation](../xtr-http-message) come with the package: the
   [messages](#the-request-and-the-response-as-messages) are part of what it does. So does the
   parser a submitted form with files in it is read with: building the request as a message
   asks the web framework for the form behind every multipart body, and the framework refuses
@@ -470,10 +466,11 @@ removing it undoes.
   from `xtr_http_kernel.bundle`. Then call `setup(app, kernel)` where the application is built.
 - **Brings along** — the [event dispatcher](../xtr-event-dispatcher) bundle always, because the
   lifecycle dispatches through it; the [logging](../xtr-logging), [console](../xtr-console) and
-  [rate limiter](../xtr-rate-limiter) bundles whenever those packages are *installed* — they are required peers, pulled in and made
-  active without being listed, and left out silently when the package is not installed. Listing
-  is not what activates them; installing the extra is. No bundle comes along for the messages:
-  neither message package ships one, and this bundle registers their services itself.
+  [rate limiter](../xtr-rate-limiter) bundles whenever those packages are *installed* — they are
+  required peers, pulled in and made active without being listed, and left out silently when the
+  package is not installed. Listing is not what activates them; installing the package is. No
+  bundle comes along for the messages: neither message package ships one, and this bundle
+  registers their services itself.
 - **Configure** — nothing is required: the zero-config path gives every request a fresh `uuid4`
   id under `X-Request-Id` — an inbound one is not trusted — no robots header, and the `request`
   log channel, and makes the request and the response of a request askable as
@@ -485,8 +482,8 @@ removing it undoes.
 - **Remove** — drop the `setup(app, kernel)` call, drop the `BUNDLES` entry, delete
   `<app>/config/http_kernel.py` if you wrote one, then `uv remove xtr-http-kernel`.
 - **Check** — `debug:bundles` shows `http_kernel` as `listed` and `active`, `event_dispatcher`
-  as `required`, and (with the extras) `logging` and `console` as `required`; `debug:router`
-  lists the application's routes.
+  as `required`, and (when those packages are installed) `logging` and `console` as `required`;
+  `debug:router` lists the application's routes.
 
 ## Configure
 
@@ -762,7 +759,7 @@ xtr_http_kernel/
 ├── request_lifecycle_middleware.py the middleware that dispatches the events
 ├── middleware_stack.py             the ordered chain a bundle contributes to
 ├── middleware_tag.py               MIDDLEWARE_TAG, the tag bundles agree on
-├── rate_limiter/                   RateLimited, with the rate-limiter extra
+├── rate_limiter/                   RateLimited, when xtr-rate-limiter is installed
 ├── routing/                        Route, RouteCollection, Router, the loaders and configurators
 ├── command/                        debug:router and router:match
 ├── exception/                      HttpKernelError, the root of everything this library raises
@@ -776,7 +773,7 @@ Developed in the [python-xtr](https://github.com/xterr/python-xtr) monorepo, und
 repository is a read-only copy, so send issues and pull requests to the monorepo.
 
 ```sh
-uv sync --all-extras
+uv sync
 uv run ruff check
 uv run ruff format --check
 uv run basedpyright

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/README.md

@@ -38,16 +38,17 @@ Listeners are services, so they come from the container with everything else the
 ## Install
 
 ```sh
-uv add xtr-http-kernel                      # the lifecycle, its bundle and setup
-uv add "xtr-http-kernel[logging]"           # + the listeners that log
-uv add "xtr-http-kernel[console]"           # + the commands that report on the router
-uv add "xtr-http-kernel[rate-limiter]"      # + rate limits on routes, routers and the app
+uv add xtr-http-kernel     # the lifecycle, its bundle and setup
+uv add xtr-logging         # beside it: the listeners that log
+uv add xtr-console         # beside it: the commands that report on the router
+uv add xtr-rate-limiter    # beside it: rate limits on routes, routers and the app
 ```
 
 Requires Python 3.11+. The web framework and the container layer come with the package
-itself — this *is* the integration — so neither is an extra, and neither is the
-[HTTP message contract](../xtr-http-message-contracts) or
-[its implementation](../xtr-http-message): the bridge below is made of them.
+itself — this *is* the integration — and so do the
+[HTTP message contract](../xtr-http-message-contracts) and
+[its implementation](../xtr-http-message): the bridge below is made of them. The three
+packages beside it are optional: each is used when it is installed and left alone when not.
 
 ## Quick start
 
@@ -338,9 +339,10 @@ id. The request id settles right after the unit opens, for the same reason.
 
 ## Rate limits
 
-With the `rate-limiter` extra, a route, a router or the whole application can be held to a
-limiter configured in [xtr-rate-limiter](../xtr-rate-limiter)'s bundle. `RateLimited` is one
-declaration, written as a decorator or wherever the framework takes a dependency:
+With [xtr-rate-limiter](../xtr-rate-limiter) installed beside this package, a route, a router or
+the whole application can be held to a limiter configured in that package's bundle.
+`RateLimited` is one declaration, written as a decorator or wherever the framework takes a
+dependency:
 
 ```python
 from fastapi import APIRouter, FastAPI, Request
@@ -417,11 +419,12 @@ Everything adding this package to an application on
 [xtr-dependency-injection](../xtr-dependency-injection) takes — and, read backwards, what
 removing it undoes.
 
-- **Install** — `uv add "xtr-http-kernel[logging,console]"`; `logging` brings the listeners
-  that write to a log, `console` the commands that report on the router, `rate-limiter` the
-  [rate limits](#rate-limits). None is needed to serve requests. The
+- **Install** — `uv add xtr-http-kernel`; install [xtr-logging](../xtr-logging) beside it for
+  the listeners that write to a log, [xtr-console](../xtr-console) for the commands that report
+  on the router, [xtr-rate-limiter](../xtr-rate-limiter) for the [rate limits](#rate-limits).
+  None is needed to serve requests. The
   [HTTP message contract](../xtr-http-message-contracts) and
-  [its implementation](../xtr-http-message) come with the package, not behind an extra: the
+  [its implementation](../xtr-http-message) come with the package: the
   [messages](#the-request-and-the-response-as-messages) are part of what it does. So does the
   parser a submitted form with files in it is read with: building the request as a message
   asks the web framework for the form behind every multipart body, and the framework refuses
@@ -433,10 +436,11 @@ removing it undoes.
   from `xtr_http_kernel.bundle`. Then call `setup(app, kernel)` where the application is built.
 - **Brings along** — the [event dispatcher](../xtr-event-dispatcher) bundle always, because the
   lifecycle dispatches through it; the [logging](../xtr-logging), [console](../xtr-console) and
-  [rate limiter](../xtr-rate-limiter) bundles whenever those packages are *installed* — they are required peers, pulled in and made
-  active without being listed, and left out silently when the package is not installed. Listing
-  is not what activates them; installing the extra is. No bundle comes along for the messages:
-  neither message package ships one, and this bundle registers their services itself.
+  [rate limiter](../xtr-rate-limiter) bundles whenever those packages are *installed* — they are
+  required peers, pulled in and made active without being listed, and left out silently when the
+  package is not installed. Listing is not what activates them; installing the package is. No
+  bundle comes along for the messages: neither message package ships one, and this bundle
+  registers their services itself.
 - **Configure** — nothing is required: the zero-config path gives every request a fresh `uuid4`
   id under `X-Request-Id` — an inbound one is not trusted — no robots header, and the `request`
   log channel, and makes the request and the response of a request askable as
@@ -448,8 +452,8 @@ removing it undoes.
 - **Remove** — drop the `setup(app, kernel)` call, drop the `BUNDLES` entry, delete
   `<app>/config/http_kernel.py` if you wrote one, then `uv remove xtr-http-kernel`.
 - **Check** — `debug:bundles` shows `http_kernel` as `listed` and `active`, `event_dispatcher`
-  as `required`, and (with the extras) `logging` and `console` as `required`; `debug:router`
-  lists the application's routes.
+  as `required`, and (when those packages are installed) `logging` and `console` as `required`;
+  `debug:router` lists the application's routes.
 
 ## Configure
 
@@ -725,7 +729,7 @@ xtr_http_kernel/
 ├── request_lifecycle_middleware.py the middleware that dispatches the events
 ├── middleware_stack.py             the ordered chain a bundle contributes to
 ├── middleware_tag.py               MIDDLEWARE_TAG, the tag bundles agree on
-├── rate_limiter/                   RateLimited, with the rate-limiter extra
+├── rate_limiter/                   RateLimited, when xtr-rate-limiter is installed
 ├── routing/                        Route, RouteCollection, Router, the loaders and configurators
 ├── command/                        debug:router and router:match
 ├── exception/                      HttpKernelError, the root of everything this library raises
@@ -739,7 +743,7 @@ Developed in the [python-xtr](https://github.com/xterr/python-xtr) monorepo, und
 repository is a read-only copy, so send issues and pull requests to the monorepo.
 
 ```sh
-uv sync --all-extras
+uv sync
 uv run ruff check
 uv run ruff format --check
 uv run basedpyright

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "xtr-http-kernel"
-version = "4.0.4"
+version = "4.1.0"
 description = "Requests turned into responses through events: a request lifecycle for FastAPI applications on the xtr kernel."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -27,7 +27,7 @@ classifiers = [
 dependencies = [
     "fastapi>=0.121.3",
     "starlette>=0.40",
-    "xtr-dependency-injection[fastapi]>=4.0,<5",
+    "xtr-dependency-injection>=4.0,<5",
     "xtr-event-dispatcher>=4.0,<5",
     "xtr-event-dispatcher-contracts>=4.0,<5",
     "xtr-http-message>=4.0,<5",
@@ -42,14 +42,6 @@ dependencies = [
 name = "Xterr"
 email = "me@xterr.dev"
 
-[project.optional-dependencies]
-logging = ["xtr-logging>=4.0,<5"]
-console = ["xtr-console>=4.0,<5"]
-rate-limiter = [
-    "xtr-clock>=4.0,<5",
-    "xtr-rate-limiter[di]>=4.0,<5",
-]
-
 [project.entry-points."xtr_dependency_injection.bundles"]
 http_kernel = "xtr_http_kernel.bundle:HttpKernelBundle"
 
@@ -67,7 +59,7 @@ dev = [
     "xtr-logging>=4.0,<5",
     "xtr-console>=4.0,<5",
     "xtr-clock>=4.0,<5",
-    "xtr-rate-limiter[di]>=4.0,<5",
+    "xtr-rate-limiter>=4.0,<5",
     "httpx>=0.27",
 ]
 

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "xtr-http-kernel"
-version = "4.0.4"
+version = "4.1.0"
 description = "Requests turned into responses through events: a request lifecycle for FastAPI applications on the xtr kernel."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -26,7 +26,7 @@ dependencies = [
     "fastapi>=0.121.3",
     # Imported directly — requests, responses, middleware — not only through fastapi.
     "starlette>=0.40",
-    "xtr-dependency-injection[fastapi]>=4.0,<5",
+    "xtr-dependency-injection>=4.0,<5",
     "xtr-event-dispatcher>=4.0,<5",
     "xtr-event-dispatcher-contracts>=4.0,<5",
     # The bridge builds messages and is the one place a message meets a route,
@@ -44,18 +44,6 @@ dependencies = [
     "python-multipart>=0.0.18",
 ]
 
-[project.optional-dependencies]
-logging = [
-    "xtr-logging>=4.0,<5",
-]
-console = [
-    "xtr-console>=4.0,<5",
-]
-rate-limiter = [
-    "xtr-clock>=4.0,<5",
-    "xtr-rate-limiter[di]>=4.0,<5",
-]
-
 # Advertises the bundle so debug:bundles can name it when installed but not listed.
 # Advertising activates nothing: an application lists the bundles it wants.
 [project.entry-points."xtr_dependency_injection.bundles"]
@@ -76,7 +64,7 @@ dev = [
     "xtr-logging>=4.0,<5",
     "xtr-console>=4.0,<5",
     "xtr-clock>=4.0,<5",
-    "xtr-rate-limiter[di]>=4.0,<5",
+    "xtr-rate-limiter>=4.0,<5",
     # Requests are driven straight at the application through an ASGI
     # transport, so the suite never binds a socket.
     "httpx>=0.27",

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/src/xtr_http_kernel/.agents/skills/xtr-http-kernel/SKILL.md

@@ -253,8 +253,8 @@ gone caller or a shutdown reached the lifecycle, not that anything is broken.
 
 ## Rate limits
 
-With the `rate-limiter` extra, `RateLimited` holds a route, a router or the whole application to
-a limiter configured in xtr-rate-limiter's bundle:
+With xtr-rate-limiter installed beside this package, `RateLimited` holds a route, a router or the
+whole application to a limiter configured in xtr-rate-limiter's bundle:
 
 ```python
 from xtr_http_kernel.rate_limiter import RateLimited
@@ -324,15 +324,15 @@ tests serving one application must not run at the same time.
 `HttpKernelBundle`. That is the steps below a recipe can do; the `setup(app, kernel)` step it
 prints for you to make.
 
-1. **Install** `uv add "xtr-http-kernel[logging,console]"`. The extras: `logging` adds the
-   listeners that write to a log, `console` the router commands, `rate-limiter` the rate limits.
-   None is needed to serve requests. The two message packages come with it, not behind an extra,
-   and so does the parser a submitted form with files in it is read with: building the request as
-   a message asks the framework for the form behind every multipart body.
+1. **Install** `uv add xtr-http-kernel`. Installed beside it, xtr-logging adds the listeners that
+   write to a log, xtr-console the router commands, xtr-rate-limiter the rate limits. None is
+   needed to serve requests. The two message packages come with it, and so does the parser a
+   submitted form with files in it is read with: building the request as a message asks the
+   framework for the form behind every multipart body.
 2. **Activate** `HttpKernelBundle: {"all": True}` in `BUNDLES` in `<app>/bundles.py`, imported
    from `xtr_http_kernel.bundle`, then call `setup(app, kernel)` where the application is built.
 3. **Brings along** the event dispatcher bundle always; the logging, console and rate limiter
-   bundles whenever those packages are installed. Installing the extra is what activates them,
+   bundles whenever those packages are installed. Installing the package is what activates them,
    not listing.
 4. **Configure** nothing by default: a fresh `uuid4` id under
    `X-Request-Id` per request (an inbound one is not trusted), no robots header, the `request`

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/src/xtr_http_kernel/.agents/skills/xtr-http-kernel/references/rate-limits.md

@@ -1,7 +1,7 @@
 # Rate limits
 
-Needs the `rate-limiter` extra (`uv add "xtr-http-kernel[rate-limiter]"`) and limiters
-configured in [xtr-rate-limiter](https://github.com/xterr/python-xtr-rate-limiter)'s bundle.
+Needs [xtr-rate-limiter](https://github.com/xterr/python-xtr-rate-limiter) installed beside this
+package (`uv add xtr-rate-limiter`) and limiters configured in its bundle.
 `RateLimited` names one of those limiters; everything else is where you put the declaration.
 
 ```python

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/src/xtr_http_kernel/bundle/http_kernel_bundle.py

@@ -162,8 +162,8 @@ class HttpKernelBundle(Bundle[HttpKernelConfig]):
             .add_tag(LISTENER_TAG, event=ResponseEvent, method="on_response")
         )
         if bundle_active(builder, "logging"):
-            # Needs the optional logging extra, which being here proves installed.
-            from xtr_http_kernel.event_listener.log_unit_listener import (  # noqa: PLC0415 — optional extra
+            # Needs xtr-logging, which the logging bundle being active proves installed.
+            from xtr_http_kernel.event_listener.log_unit_listener import (  # noqa: PLC0415 — xtr-logging is optional
                 LogUnitListener,
             )
 
@@ -186,7 +186,8 @@ class HttpKernelBundle(Bundle[HttpKernelConfig]):
                 LISTENER_TAG, event=ExceptionEvent, method="on_exception"
             )
         if bundle_active(builder, "rate_limiter"):
-            # Reads what the rate-limit dependency leaves on a request; the extra is installed.
+            # Reads what the rate-limit dependency leaves on a request; xtr-rate-limiter is
+            # installed, since its bundle is active.
             from xtr_http_kernel.event_listener.rate_limit_headers_listener import (  # noqa: PLC0415
                 RateLimitHeadersListener,
             )

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/src/xtr_http_kernel/event_listener/__init__.py

@@ -6,8 +6,8 @@ page out of a search index, a unit of work per request. The bundle registers
 them; outside a container each is an ordinary object to register by hand.
 
 :class:`~xtr_http_kernel.event_listener.log_unit_listener.LogUnitListener`
-is not re-exported here: it needs the optional logging extra, so it is
-imported from its own module by whoever knows that extra is installed.
+is not re-exported here: it needs xtr-logging, which is optional, so it is
+imported from its own module by whoever knows xtr-logging is installed.
 """
 
 from __future__ import annotations

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/src/xtr_http_kernel/event_listener/log_unit_listener.py

@@ -1,7 +1,7 @@
 """Each request framed as one unit of work for the logging package.
 
-This module needs the optional logging extra: it is deliberately left out of
-the package's eager re-exports, and the bundle registers the listener only
+This module needs xtr-logging, which is optional: it is deliberately left out
+of the package's eager re-exports, and the bundle registers the listener only
 when the logging bundle is active.
 """
 

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/src/xtr_http_kernel/event_listener/request_id_listener.py

@@ -18,13 +18,13 @@ __all__ = ["RequestIdListener"]
 _VALID_REQUEST_ID: Final = re.compile(r"[A-Za-z0-9._-]{1,200}")
 """What an incoming id may look like before it is worth keeping."""
 
-# Binding the id to the ambient log context is a courtesy to the logging
-# package, which is an optional extra: without it there is nothing to bind to
-# and the listener still does its job.
+# Binding the id to the ambient log context is a courtesy to xtr-logging,
+# which is optional: without it installed there is nothing to bind to and the
+# listener still does its job.
 _bind_context: Callable[[Context], None] | None
 try:
     from xtr_logging import bind_context as _bind_context
-except ImportError:  # pragma: no cover — exercised only without the logging extra.
+except ImportError:  # pragma: no cover — exercised only without xtr-logging installed.
     _bind_context = None
 
 

{xtr_http_kernel-4.0.4 → xtr_http_kernel-4.1.0}/src/xtr_http_kernel/rate_limiter/__init__.py

@@ -1,7 +1,7 @@
 """Rate limits on routes, routers and whole applications, through the rate limiter bundle.
 
-Needs the ``rate-limiter`` extra, which brings xtr-rate-limiter; importing
-this package without it fails, which is why nothing else here imports it.
+Needs xtr-rate-limiter, installed beside this package; importing this
+package without it fails, which is why nothing else here imports it.
 """
 
 from __future__ import annotations