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 MyoFInDer, a pyproject.toml file was added since the very first release 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. This will allow to get rid of the setup.py file, and of the requirements.txt as well.
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. Thesetup.py
file should now be used only for complex builds with thesetuptools
backend.In MyoFInDer, a
pyproject.toml
file was added since the very first release 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.py
topyproject.toml
. This will allow to get rid of thesetup.py
file, and of therequirements.txt
as well.