Modernize the build and use pyproject.toml instead of setup.py #558
Description
When pip is updated to version 25.2, the Docker build logs show:
DEPRECATION: Legacy editable install of oioioi=0.2.0.dev0 from file:///sio2/oioioi (from -r requirements.txt (line 8)) (setup.py develop) is deprecated. pip 25.3 will enforce this behaviour change. A possible replacement is to add a pyproject.toml (e.g. --use-pep517, and use setuptools >= 64. If the resulting installation is not behaving as expected, try using --config-settings editable=compat. Please consult the setuptools documentation for more information. Discussion can be found at https://github.com/pypa/pip/issues/11457
a similar warning regarding dependencies:
DEPRECATION: Building 'sioworkers' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the --use-pep517 option, (possibly combined with --no-build-isolation), or adding a pyproject.toml file to the source tree of 'sioworkers'. Discussion can be found at https://github.com/pypa/pip/issues/6334
setup.py bdist_wheel applies to: sioworkers, simplejson, django-ranged-response, fpdf, unicodecsv, coreschema.
Using setup.py develop is deprecated, moreover setup.py is an old method (but not deprecated) of creating entry points and defining dependencies (as mentioned in #556).
Already in https://github.com/sio2project/filetracker, setup.py was removed sio2project/filetracker#82.
I think it’s a good idea to modernize the build process (e.g. by using pyproject.toml instead of setup.py).
At the same time, I’d consider whether some of those ancient dependencies (mentioned above) could be replaced with something newer, or whether we could make use of existing dependencies and modern Python.
See: https://packaging.python.org/en/latest/guides/modernize-setup-py-project/