CodeVetter · Repo Unpack · System map
pydantic/pydantic-settings
The runtime is an importable Python package whose primary boundary is model construction. BaseSettings orchestrates source selection and merging, while source modules own input acquisition and preparation. CLI execution adds parser and command-dispatch boundaries around the same settings machinery. Packaging, development checks, documentation rendering, and tagged releases are configured separately.
- The package initializer exposes BaseSettings, SettingsConfigDict, CliApp, source providers, CLI annotations, decoding markers, and version metadata as the public import surface.
- BaseSettings subclasses Pydantic BaseModel; its constructor prepares sources, merges their mappings, and passes the result to BaseModel.__init__ for validation.
- PydanticBaseSettingsSource defines the dictionary-producing source contract, field acquisition/preparation hooks, and access to prior aggregate and per-source state.
- Environment, dotenv, and flat secret sources are built into construction; JSON, TOML, YAML, pyproject, nested secrets, and cloud integrations are additional source classes selected through customization.
- Runtime retention includes a process-local settings cache keyed by exact model class and separate per-class construction locks; source mappings and merge state otherwise belong to settings resolution.
- Hatchling builds the distribution and reads its dynamic version from version.py; the manifest requires Python >=3.10, Pydantic >=2.7.0, python-dotenv, typing-extensions, and typing-inspection.
- Optional extras supply YAML, TOML, Azure, AWS, and GCP dependencies; Makefile development commands use uv for installation, Ruff lint/format checks, mypy, and pytest under coverage.
- Documentation uses strict MkDocs Material configuration; the inspected CI publishes a built package to PyPI only for tags after its aggregate check succeeds, using a release environment and OIDC permission.