Skip to main content

Typed Settings

Load and merge settings from multiple different sources and present them in a structured, typed, and validated way!

Why?

There are many different config file formats and libraries. Many of them have a narrow scope, don't integrate well with other libs, or lack in typing support.

Typed Settings' goal is to enable you to load settings from any source (e.g., env vars, config files, vaults) and can convert values to anything you need.

You can extend Typed Settings to support config sources that aren't supported yet and its extensive documentation will help you on your way.

What can it be used for?

You can use Typed Settings in any context, e.g.:

  • server processes
  • containerized apps
  • command line applications
  • scripts and tools for scientific experiments and data analysis

What does it do?

  • It loads settings from multiple sources (e.g., env vars, config files, secret vaults) in a unified way and merges the loaded values. You can add loaders for sources we cannot imagine yet.

  • It can post-process loaded values. This allows value interpolation/templating or calling helpers that retrieve secrets from vaults. You can create and add any processors you can image if the built-in ones are not enough.

  • You can add a CLI on top to let users update the loaded settings via command line arguments. Click and argparse are currently supported.

  • Settings are cleanly structured and typed. The type annotations are used to convert the loaded settings to the proper types. This also includes higher level structures like dates, paths and various collections (lists, dicts, …). You can use attrs, dataclasses, or Pydantic to write settings classes.

    Types Settings uses the powerful and fast cattrs) by default and falls back to an internal converter if cattrs is not installed.

  • No mandatory requirements. Typed Settings works out-of-the box with dataclasses, argparse and its own converter.

The documentation contains a full list of all features.

Installation

Install and update using pip:

$ python -m pip install typed-settings

Typed Settings as no required dependencies. You can install dependencies for optional features via

$ python -m pip install typed-settings[<feature>,...]

Available features:

  • typed-settings[attrs]: Enable settings classes via attrs.
  • typed-settings[pydantic]: Enable settings classes via Pydantic.
  • typed-settings[cattrs]: Enable usage of the powerful and fast cattrs converter.
  • typed-settings[click]: Enable support for Click options.
  • typed-settings[option-groups]: Enable support for Click and Click option groups.
  • typed-settings[dotenv]: Enable support for reading .env files via python-dotenv.
  • typed-settings[orjson]: Use orjson instead of the built-in json module for loading JSON files.
  • typed-settings[yaml]: Enable support for loading YAML files.
  • typed-settings[jinja]: Enable support for value interpolation with Jinja templates.
  • typed-settings[all]: Install all optional requirements.

Examples

Hello, World!, with env. vars.

This is a very simple example that demonstrates how you can load settings from environment variables.

# example.py
import attrs
import typed_settings as ts

@attrs.frozen
class Settings:
    option: str

settings = ts.load(cls=Settings, appname="example")
print(settings)
$ EXAMPLE_OPTION="Hello, World!" python example.py
Settings(option='Hello, World!')

Nested classes and config files

Settings classes can be nested. Config files define a different section for each class.

# example.py
import attrs
import click

import typed_settings as ts

@attrs.frozen
class Host:
    name: str
    port: int

@attrs.frozen
class Settings:
    host: Host
    endpoint: str
    retries: int = 3

settings = ts.load(
    cls=Settings, appname="example", config_files=["settings.toml"]
)
print(settings)
# settings.toml
[example]
endpoint = "/spam"

[example.host]
name = "example.com"
port = 443
$ python example.py
Settings(host=Host(name='example.com', port=443), endpoint='/spam', retries=3)

Configurable settings loaders

The first example used a convenience shortcut with pre-configured settings loaders. However, Typed Settings lets you explicitly configure which loaders are used and how they work:

# example.py
import attrs
import typed_settings as ts

@attrs.frozen
class Settings:
    option: str

settings = ts.load_settings(
    cls=Settings,
    loaders=[
        ts.FileLoader(
            files=[],
            env_var="EXAMPLE_SETTINGS",
            formats={
                "*.toml": ts.TomlFormat("example"),
            },
        ),
        ts.EnvLoader(prefix="EXAMPLE_"),
      ],
)
print(settings)
$ EXAMPLE_OPTION="Hello, World!" python example.py
Settings(option='Hello, World!')

In order to write your own loaders or support new file formats, you need to implement the Loader or FileFormat protocols.

You can also pass a custom cattrs converter to add support for additional Python types.

Command Line Interfaces

Typed Settings can generate a command line interfaces (CLI) based on your settings. These CLIs will load settings as described above and let users override the loades settings with command line argumments.

Typed Settings supports argparse and click.

Argparse

# example.py
import attrs
import typed_settings as ts

@attrs.frozen
class Settings:
    a_str: str = ts.option(default="default", help="A string")
    an_int: int = ts.option(default=3, help="An int")

@ts.cli(Settings, "example")
def main(settings):
    print(settings)

if __name__ == "__main__":
    main()
$ python example.py --help
usage: example.py [-h] [--a-str TEXT] [--an-int INT]

options:
  -h, --help    show this help message and exit

Settings:
  Settings options

  --a-str TEXT  A string [default: default]
  --an-int INT  An int [default: 3]
$ python example.py --a-str=spam --an-int=1
Settings(a_str='spam', an_int=1)

Click

# example.py
import attrs
import click
import typed_settings as ts

@attrs.frozen
class Settings:
    a_str: str = ts.option(default="default", help="A string")
    an_int: int = ts.option(default=3, help="An int")

@click.command()
@ts.click_options(Settings, "example")
def main(settings):
    print(settings)

if __name__ == "__main__":
    main()
$ python example.py --help
Usage: example.py [OPTIONS]

Options:
  --a-str TEXT      A string  [default: default]
  --an-int INTEGER  An int  [default: 3]
  --help            Show this message and exit.
$ python example.py --a-str=spam --an-int=1
Settings(a_str='spam', an_int=1)

Metadata

Release files for typed-settings 26.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for typed-settings 26.1.0
File Size Uploaded Provenance Actions
typed_settings-26.1.0.tar.gz 3.5 MB Without provenance Details for typed_settings-26.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for typed-settings 26.1.0
File Interpreter ABI Platform Actions
typed_settings-26.1.0-py3-none-any.whl Python 3 none any Details for typed_settings-26.1.0-py3-none-any.whl

Total release size: 3.6 MB

Release files / typed_settings-26.1.0.tar.gz

Download URL typed_settings-26.1.0.tar.gz
Size 3.5 MB
Tags Source
SHA-256 checksum
How to use checksums
ebd8fbcf8d314f922a7f0307f622a482dc3a6eacdef6ea644d39a4dc2a41b049
BLAKE2b-256 checksum
How to use checksums
c81677a76793dd600c2df4fab91b26b5f15f121eeea7b86ba46edd4c13a7957b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.9 {"installer":{"name":"uv","version":"0.12.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / typed_settings-26.1.0-py3-none-any.whl

Download URL typed_settings-26.1.0-py3-none-any.whl
Size 65.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7f6504e0aea41668b6cac4d3d6b72047302e063084acd23c97dcb69247c7c702
BLAKE2b-256 checksum
How to use checksums
ad836c905979732f743ab150cf71bc9d223272172621b5e6b1ecf9359ae9d15d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.9 {"installer":{"name":"uv","version":"0.12.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for typed-settings 26.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

26.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page