tomli VS spock

But the whitespace handling involved is an extra complication, at least the provided example fails to be parsed by `tomli`, which is following the currently release TOML spec: https://github.com/hukkin/tomli/issues/199

ini files aren't standardized, the syntax is really "whatever the parser implements". For new projects I recommend using toml instead. It's ini-like, but standardized. Python 3.11 even comes with a builtin parser tomllib (earlier python versions can use tomli, which is what tomllib is based on).

tomllib is primary the library tomli: https://github.com/hukkin/tomli

TOML as a format is by default used by many Python tools, including build tools. This creates a bootstrapping problem for them. Additionally, many popular tools such as flake8 don't include TOML support citing its lack of support in standard library. This PEP proposes to add TOML support to standard library based on tomli which is already used by packages such as pip or pytest.

tomli Relatively fast read-only parsing. Companion library tomli-w for writing.

(Note: I wrote a library called spock that was originally based on dataclasses and then shifted to attrs. In the end attrs was just the better and more fully fledged library for what I needed so I’ve always preferred attrs over dataclasses since then)

Spock-Config allows one to create OO configuration files. That's how I roll. I currently use PYdantic settings and it's great. But it does not offer command-line re-configuration of what you have in the OO config file.

Check out more in the docs or on GitHub

We wrote Spock which actually sits in the middle ground between Hydra and OmegaConf (I’m of the same opinion that Hydra does a little too much feature wise). You can do hierarchical composition within the markdown of any JSON, YAML, or TOML files by simply using the config argument. No code needed to merge. Docs are here if you’re interested.

Spock