After the changes to Python's packages build system brought in PEP 518, and later PEP 517 and PEP 621, the standard way to provide information to the build system is to use a pyproject.toml file. The setup.py file should now be used only for complex builds with the setuptools backend.
In Crappy, a pyproject.toml file was added in version 1.4.2 for building the tarball and the wheel before uploading to PyPI. It only contains the minimal mandatory fields for building with setuptools, but all the metadata is still contained in setup.py.
To keep the project up-to-date with the evolution of the build system in Python, the project metadata should be moved from setup.py to pyproject.toml. As some objects in Crappy still require extension modules managed by setup.py, both setup.py and pyproject.toml will still co-exist in the project after the migration. The objects depending on extension modules might however be removed in future releases, making it possible to ultimately keep only a pyproject.toml file.
After the changes to Python's packages build system brought in PEP 518, and later PEP 517 and PEP 621, the standard way to provide information to the build system is to use a
pyproject.tomlfile. Thesetup.pyfile should now be used only for complex builds with thesetuptoolsbackend.In Crappy, a
pyproject.tomlfile was added in version 1.4.2 for building the tarball and the wheel before uploading to PyPI. It only contains the minimal mandatory fields for building with setuptools, but all the metadata is still contained insetup.py.To keep the project up-to-date with the evolution of the build system in Python, the project metadata should be moved from
setup.pytopyproject.toml. As some objects in Crappy still require extension modules managed bysetup.py, bothsetup.pyandpyproject.tomlwill still co-exist in the project after the migration. The objects depending on extension modules might however be removed in future releases, making it possible to ultimately keep only apyproject.tomlfile.