Supporting configuration from pyproject.toml

[ikollipara]

Currently the project supports a wide range of .ini-style configurations. However, the direction that many tools (black, ruff, coverage, etc.) are moving is to having a defined configuration in the pyproject.toml. Given that python now features a built-in package for reading .toml files (tomllib) I think it shouldn't be too difficult to pull the configuration from there.

The main consideration is where in the resolution order does the pyproject.toml go. I'm in favor of it being the second to last place for configuration, to push new users towards it.

But I'm completely open to thoughts, what do you think?

[sodul]

I agree that adding support for pyproject.toml makes sense.

Unfortunately tomllib was only added to the standard library in 3.11 and we are currently backward compatible with 3.8, or soon 3.9 since 3.8 is now deprecated upstream.

https://docs.python.org/3/library/tomllib.html

This means that for versions prior to 3.11 we will need to add an explicit dependency on tomllib, which should be fine.

I would look at what other projects are doing for resolution order (mypy, pylint, ruff, black), if they are consistent then I would recommend to stay consistent, if not then we can pick whatever is making the most sense for green.