Moved the metadata from setup.cfg into PEP 621-compliant pyproject.toml

[KOLANICH]

No description provided.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[viraptor]

Is there are reason to do this now? What's the minimum python to deal with this?

[KOLANICH]

As you see, there are 2 commits. It is intentional, these commits should NOT be collapsed into a single one.

1. One migrates the metadata into setup.cfg, which is in fact available in setuptools from Dec 2016, but we set the requirements to a later version of setuptools, because the one from 2016 doesn't allow to get rid of setup.py entirely, but 43.0.0, which python_requires = >=2.7,!=3.0.*,!=3.1.*,!=3.2.*,!=3.3.* does.
2. Another one migrates the metadata into pyproject.toml, which is a standard (PEP 621) way to store the metadata now, which is compatible to setuptools, flit and maturin PEP 517 build frontends. poetry is on the way. It requires setuptools>=61.2.0, which python_requires = >=3.7. Obviously, Windows XP users (which maximum CPythkn version is 3.4) are thrown into a dumpster with building, but I think we can try to backport this setuptools to 3.4, usually python version is raised because of bullshit bells-and-whistles features like f-strings (and I guess we can fully automatically rewrite them into format calls) and cool features like type annotations (but there is a 3.4-compatible way, called type comments, with built-in support in ast module). Anyway, this only restricts building, the wheels are compatible to the python version stated in them, the most of users use prebuilt wheels from pypi, and even if they need the latest version from git, noone disallows them to fetch the wheel, unpack it, replace the source files in it and pack it back.

[viraptor]

Cool, thanks. Since this isn't urgent, I think I'll wait until April 2023, when ubuntu LTS drops python 3.6.

[KOLANICH]

The first commit can be merged right now.

[thesamesam]

Cool, thanks. Since this isn't urgent, I think I'll wait until April 2023, when ubuntu LTS drops python 3.6.

Would this be okay to merge now?