modern-di-aiohttp 2.2.0 — adopt the modern-di integration kit
Maintenance release. No public API change — FromDI, inject,
setup_di, fetch_di_container, fetch_request_container, and the
connection providers keep their signatures and behavior. Swaps this
package's hand-rolled connection dispatch and marker resolution for the
shared primitives in
modern_di.integrations,
shipped in
modern-di 2.28.0.
Fourth of 13 planned adapter conversions across the modern-di ecosystem
(after
modern-di-starlette 2.2.0,
modern-di-fastapi 2.10.0,
and
modern-di-litestar 2.13.0).
Internal refactors
_di_middlewarekeeps its owncan_prepare()handshake probe to
selectaiohttp_websocket_provideroraiohttp_request_provider— this
package is a documented outlier: both providers bindweb.Request(a
WebSocket is an upgraded HTTP request at aiohttp's middleware entry
point), sointegrations.classify_connection's isinstance-over-tuple
dispatch cannot distinguish them. Once the provider is picked,
integrations.bind(provider, request)now derives the scope/context
the middleware used to hand-write.bind()never returnsNone, so no
fallback branch is needed.- The child container's manual
try/finally: await child_container.close_async()is nowContainer's ownasync with—
entering an already-open container is a no-op; exiting closes it,
including on the exception path. _FromDI/_parse_inject_params/_resolve_di_paramsare gone.
FromDI = integrations.from_di;injectnow composes
integrations.parse_markers/integrations.resolve_markers.
Packaging
- Bumps the
modern-difloor to>=2.28.0,<3.
Downstream
No action needed — the public API (FromDI, inject, setup_di,
fetch_di_container, fetch_request_container,
aiohttp_request_provider/aiohttp_websocket_provider) is unchanged.
Upgrading only requires modern-di>=2.28.0.
Internals
- 100% line coverage;
ruff,tyclean across Python 3.10–3.14. - Built via
subagent-driven-development: 5 planned tasks, each with an
independent spec+quality review; a whole-branch review before merge.