Migrate to pyproject.toml

[deronnax]

It's the future. The setup.cfg needs to stay because flake8 refuses to migrate to pyproject.toml. The tox config stays there as well, as tox config in pyproject.toml is currently basically inlined tox setup.cfg config.

[pbiering]

This change can cause issues in external packaging (e.g. RPM or DEB) which need to be potentially adjusted, postponed to 3.3.0 to avoid such potential unexpected change in a very minor version.

[deronnax]

when is 3.3.0 coming ?

[pbiering]

when is 3.3.0 coming ?

only code-related outstandings are this and your other PR, but these can be postponed to 3.3.x if you wish

[deronnax]

let's get it merged for 3.3.0

[pbiering]

regarding requires = ["setuptools>=61.2"] -> this will kill EL8 support because here the latest available version is

python39-setuptools.noarch   50.3.2-6.module_el8.10.0+3885+d986a391   @appstream

Would it be possible to support both methods? I do not like to introduce for RPM packaging for radicale/EL8 the same as I already did for mailmain3 (huge amount of workarounds, even for EL9 in this case).

How urgent is this change to "pyproject.toml"?

[pbiering]

regarding requires = ["setuptools>=61.2"]

Hmm, saw now that meanwhile Python 3.11 arrived in EL8 and EL9

python3.11-setuptools.noarch    65.5.1-3.el8_10    appstream  
python3.12-setuptools.noarch    68.2.2-4.el8_10    appstream  

python3.11-setuptools.noarch    65.5.1-2.el9_4.1   appstream
python3.12-setuptools.noarch    68.2.2-3.el9_4.1   appstream

So in case this PR is applied, packaging for EL8+9 has to change then from Python 3.9 to 3.11 - should be not a big deal.

[deronnax]

what is EL8 ?

[pbiering]

what is EL8 ?

Enterprise Linux major version 8 - Red Hat, Alma, Rocky...

[pbiering]

@deronnax : please rebase to latest, currently your branch has conflicts

[pbiering]

@deronnax can you please dig into why the "lint" test failed?

[pbiering]

@deronnax this broke more now...can you try to run test suite locally (https://github.com/Kozea/Radicale/wiki/Development-Testing-Release#complete-test-suite) to fix this

[pbiering]

ok