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
Configuration is the dependency almost every graph has, and today it is wired
the same way as anything else — a Factory over a function the application
writes. A first-class provider for pydantic-settings, environment variables, or
TOML would remove that boilerplate.
What it must clear first
The conservative feature set
bar: a new provider type is added only when the existing primitives genuinely
cannot solve the task. A Factory wrapping Settings() already solves the
common case, so a proposal has to show what it cannot express. The
zero-dependency guarantee also rules out a hard dependency on
pydantic-settings or a TOML library in core.
Revisit trigger
A design that stays zero-dependency and expresses something Factory cannot.
Migrated from
ROADMAP.md's## Under considerationsection, which is being deleted — an unscheduled item belongs in the tracker, not in a third hand-maintained file. See #438.Why it is open
Configuration is the dependency almost every graph has, and today it is wired
the same way as anything else — a
Factoryover a function the applicationwrites. A first-class provider for pydantic-settings, environment variables, or
TOML would remove that boilerplate.
What it must clear first
The conservative feature set
bar: a new provider type is added only when the existing primitives genuinely
cannot solve the task. A
FactorywrappingSettings()already solves thecommon case, so a proposal has to show what it cannot express. The
zero-dependency guarantee also rules out a hard dependency on
pydantic-settings or a TOML library in core.
Revisit trigger
A design that stays zero-dependency and expresses something
Factorycannot.