Skip to content

Official integrations: the remaining entrypoint gap (Sanic, pyTelegramBotAPI) #441

Description

@lesnik512

Migrated from ROADMAP.md's ## Under consideration section, which is being deleted — an unscheduled item belongs in the tracker, not in a third hand-maintained file. See #438.

Why it is open

Each new entrypoint lets an existing container cover more of the stack, which is
the "one wiring, every entrypoint" bet the library is built on.

Already shipped: aiogram, aiohttp, arq, Celery, FastAPI, FastStream, Flask,
gRPC, Litestar, Starlette, taskiq, Typer (plus the modern-di-pytest plugin).
aiogram-dialog getters and callbacks are supported via the
modern_di_aiogram.dialog submodule.

The gap below is drawn from Dishka's integration set and sorted by community
demand. It is exploratory, not a queue.

Lower / niche demand:

  • Sanic — async web is already covered by FastAPI/Litestar/Starlette.
  • pyTelegramBotAPI (telebot) — older sync Telegram library.

Community-maintained if contributed (as Dishka treats them): Pyramid,
Strawberry, Quart, RQ, APScheduler, Jobify, Flet, ag2.

Not in this gap

Click is not planned — Typer already covers the CLI entrypoint and is built
on Click, so a separate adapter would be redundant. That refusal is recorded in
0027-no-click-integration;
do not re-open it here.

Revisit trigger

A concrete request for one of these frameworks, or a contributor volunteering to
build and maintain the adapter. Integrations live in their own repositories and
ship as separate modern-di-* packages — see
Writing an integration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestneeds-triageMaintainer needs to evaluate this issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions