Migrate metadata from setup.py to setup.cfg

[cclauss]

Perhaps a step towards #5836

This pull request was created using https://pypi.org/project/setuptools-py2cfg plus manual modifications.

https://setuptools.pypa.io/en/latest/userguide/quickstart.html#basic-use

We recommend users expose as much as possible configuration in a more declarative way via the pyproject.toml or setup.cfg, and keep the setup.py minimal with only the dynamic parts (or even omit it completely if applicable).

---

After a pull request like this is tested and merged, I usually do a follow-up PR like...

PEP 621: Migrate settings from setup.cfg into pyproject.toml

Migrate settings from setup.cfg into pyproject.toml using ini2toml to do the file conversion and running pyproject-fmt and then validate-pyproject in pre-commit to validate the results.

• Currently, flake8 is not yet compatible with pyproject.toml so move its settings into .flake8.

https://setuptools.pypa.io/en/latest/userguide/quickstart.html#basic-use

We recommend users expose as much as possible configuration in a more declarative way via the pyproject.toml or setup.cfg, and keep the setup.py minimal with only the dynamic parts (or even omit it completely if applicable).

Ran validate-pyproject to validate the results.

From validate-pyproject README:

With the approval of PEP 517 and PEP 518, the Python community shifted towards a strong focus on standardization for packaging software, which allows more freedom when choosing tools during development and make sure packages created using different technologies can interoperate without the need for custom installation procedures.

This shift became even more clear when PEP 621 was also approved, as a standardized way of specifying project metadata and dependencies.

validate-pyproject was born in this context, with the mission of validating pyproject.toml files, and making sure they are compliant with the standards and PEPs.

[matteius]

@cclauss I think this effort will conflict with: #5836

[cclauss]

Did you read the first line of the commit message above?

I am highly supportive of 5836 but it is failing its tests. I thought we could advance step-by-step until we can rebase 5836 in a way that passes all tests. Please feel free to close this PR with unmerged commits.

[matteius]

We can keep it open -- I am not sure what path would be better and I am not opinionated in this case. CC @kalebmckale

[cclauss]

Oh... Now that I see:

+ pip install build
# ...
-        python -m pipenv run python setup.py sdist bdist_wheel
+        python -m pipenv run python -m build

in #5836, that makes MUCH more sense.

[matteius]

We should figure out something to change this to at some point since that email list is gone.

[cclauss]

Closing in favor of #5836