update python packaging: stop using "setup.py"

[TomasTomecek]

/usr/lib/python3.11/site-packages/setuptools/config/setupcfg.py:463: SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use license_files instead.                                                                                      
  warnings.warn(msg, warning_class) 

/usr/lib/python3.11/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.                                                                         
  warnings.warn(

Adress these at minimum.

Since this affects what downstream distros have available, make sure to get a green light from downstream maintainers.

[grawlinson]

setuptools is PEP-517 compliant, so there's no issue with continuing to use setuptools.

If you like, I can file a PR that combines setup.cfg and setup.py into the recommended PEP-517 pyproject.toml.

(I'm one of the downstream maintainers of ansible-bender for Arch Linux)

[TomasTomecek]

that would be perfect and so kind of you, I'd highly appreciate that

[webknjaz]

the recommended PEP-517 pyproject.toml.

It's a bit confusing but what you're referring to is PEP 518 rather than PEP 517 which only describes the build requirements.

Note that it's entirely possible to keep setup.py and use PEP 517. The deprecated bit is only invoking it in shell directly.

pyproject.toml metadata support is still kinda in beta so you may want to be careful with it.

[webknjaz]

pyproject.toml metadata support is still kinda in beta so you may want to be careful with it.

UPD: it's no longer in beta FYI. Though I personally still prefer a dedicated setup.cfg.

FWIW here's a few new and refreshed documents we posted on PyPUG:

• https://packaging.python.org/en/latest/discussions/setup-py-deprecated/
• https://packaging.python.org/en/latest/guides/modernize-setup-py-project/