More recent versions of setuptools support specifying the project metadata in pyproject.toml (we still get a warning that support for additional setuptools specific configuration in pyproject.toml is beta).
This has two main advantages:
pip supposedly behaves a bit weird if both pyproject.toml and setup.cfg / setup.py are present (though I have no authorative source to back up that claim)
the new format is a bit more flexible (for instance, it is a bit easier to specify multiple authors)
but we can also get rid of setup.py, since recent versions of setuptools support PEP660.
I didn't modify anything else, so this should be pretty much a maintenance PR, but we should figure out a dependency policy (like, support a versions of dependencies for at least 6 or 12 months). That way, we don't have seriously old versions as minimum versions in the package metadata.
More recent versions of
setuptools
support specifying the project metadata inpyproject.toml
(we still get a warning that support for additionalsetuptools
specific configuration inpyproject.toml
is beta).This has two main advantages:
pip
supposedly behaves a bit weird if bothpyproject.toml
andsetup.cfg
/setup.py
are present (though I have no authorative source to back up that claim)but we can also get rid of
setup.py
, since recent versions ofsetuptools
support PEP660.I didn't modify anything else, so this should be pretty much a maintenance PR, but we should figure out a dependency policy (like, support a versions of dependencies for at least 6 or 12 months). That way, we don't have seriously old versions as minimum versions in the package metadata.
pre-commit run --all-files