Deeper pytest plugin: parametrized overrides, autouse scope helpers, async-fixture ergonomics

[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 modern-python/modern-di#438.

Why it is open

modern-di already ships a first-party pytest plugin, modern-di-pytest. This
item is about making it richer, not about creating it:

• parametrized overrides,
• autouse scope helpers,
• async-fixture ergonomics.

Where the work lands

modern-di-pytest is a separate repository and PyPI package, not part of
this repo. Anything actioned here ships there; this issue exists on the core
tracker only because that is where the roadmap entry lived.

Revisit trigger

A concrete ergonomics complaint against the current plugin, naming the fixture
shape that is awkward today.

[lesnik512]

This was generated by AI during triage.

Triage outcome: transfer to modern-di-pytest

Transferring rather than actioning or closing. This issue names its own misfiling:

modern-di-pytest is a separate repository and PyPI package, not part of this repo. Anything actioned here ships there; this issue exists on the core tracker only because that is where the roadmap entry lived.

Confirmed: modern-python/modern-di-pytest is one of the 13 separate modern-di-* repositories, and none of the three items here — parametrized overrides, autouse scope helpers, async-fixture ergonomics — touches modern_di/. Now that ROADMAP.md is retired (#446), the only reason it sat on the core tracker is gone.

It is not being closed: the content is real and unscheduled, and per CLAUDE.md unscheduled work lives as an issue. It just belongs on the tracker of the repository that would ship it, where a plugin user's ergonomics complaint would naturally land.

Unchanged by the move: the revisit trigger is still a concrete ergonomics complaint against the current plugin, naming the fixture shape that is awkward today — not a decision to be taken here.

Note for the destination: modern-di-pytest does not yet carry the triage state labels (needs-triage, needs-info, ready-for-agent, ready-for-human), so this arrives with enhancement only. It would be needs-info under the core repo's vocabulary.

[lesnik512]

This was generated by AI during triage.

Triage outcome: needs-info

Now that this repo carries the triage vocabulary (#33), applying the state this issue arrived without.

This is not an un-evaluated item — it was authored with its reasoning and revisit trigger already in place, and transferred here from modern-di because this is the repo that would ship it. What it waits on is a concrete complaint, not a maintainer decision.

What is established:

• The plugin exists; this is about deepening it, not creating it. All implementation is modern_di_pytest/factory.py, exposing exactly two public symbols — modern_di_fixture and expose.
• The three named items are unbuilt: parametrized overrides, autouse scope helpers, async-fixture ergonomics.
• Overrides are deliberately not re-implemented here. Users call Container.override() / reset_override() directly, per the contract in CLAUDE.md. A "parametrized overrides" proposal therefore has to say why the ergonomics belong in the adapter rather than upstream in modern-di, since this package does not own the container.

What would move it:

• A concrete ergonomics complaint naming the fixture shape that is awkward today — the conftest.py you had to write, and what you wanted to write instead.
• For each of the three items separately: they are bundled from a single roadmap line and are unlikely to share a design.

Worth splitting once a report arrives for one of them.