Support projects without setup.cfg

[duckinator]

It seems like setup.cfg is used exclusively for the project name. Providing a way to specify it in pyproject.toml might be useful, for folks not using setuptools (or who are doing a quick migration and still use setup.py).

I explicitly do not want to try to process setup.py. It can't be done without running it.

[duckinator]

This also appears specific to ZipApps.

[nbraud]

Given that people are supposed to have a pyproject.toml when using bork, I think it would indeed make sense to support configuring bork through that file.

If we do that, I think it would be a good idea to deprecate configuring bork through setup.cfg. Since that's more-or-less a breaking change, we might want to add a warning in bork v6, and stop looking at setup.cfg in bork v7 (or maybe even assert there's no bork-related config in there)

[duckinator]

@nbraud the value from setup.cfg that is used is metadata.name. e.g., from https://github.com/duckinator/bork/blob/main/setup.cfg:

[metadata]
name = bork

That's the only place it's used. Given that it's always there with setup.cfg-based setuptools configurations, and would be redundant to put in both, I'm wondering about checking pyproject.toml and falling back to setup.cfg?

[duckinator]

There's a specification for this, now: https://packaging.python.org/en/latest/specifications/declaring-project-metadata/

And setuptools is on board: https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html