toml VS tomli

Black uses by default the pyproject.toml file. This file contains a section for each different tool we want to use. The use of a configuration file like pyproject.toml is quite a good choice and helps the contributors to use the same tools and configurations you're using.

> I don't think even though TOML has some official spec

Read it on https://toml.io/ (Full spec on upper-right… with its evolutions up to final 1.00 version).

ini2toml which automatically translates .ini/.cfg files into TOML

toml 1.1 will allow non-ascii in keys (and multi-line inline tables)

See https://github.com/toml-lang/toml/blob/main/CHANGELOG.md

GitHub - toml-lang/toml: Tom's Obvious, Minimal Language

See https://github.com/toml-lang/toml/blob/main/CHANGELOG.md

> I still think it's the best format out there.

What do you think of https://toml.io ?

TOML built-in support

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.