Actions
Idea #20723
open
Stop running setup.py in our build+test infrastructure
Start date:
Due date:
Story points:
-
Description
Doing so is deprecated and also the source of some messiness. See these warnings when you test the Python SDK:
WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox. /home/brett/.cache/arvados-test/VENV3DIR/lib/python3.11/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer.
Instead of setup.py test we can use tox, python3 -m unittest.main, etc.
Instead of setup.py build / setup.py sdist we can use python3 -m build, or there might be a direct setuptools invocation too (although it'll probably be deprecated soon if it's not already).
Instead of setup.py install we can use python3 -m pip install.
This might be an epic, it might make sense to break out separate stories for individual parts like updating test infrastructure, updating build infrastructure, …
Related issues
Updated by Brett Smith over 1 year ago
- Related to Idea #20311: Update Python packages to build with PEP 517/518 added
Updated by Brett Smith about 1 year ago
- Related to Idea #21207: Decide and implement a modern way to run Python tests added
Updated by Brett Smith 6 months ago
- Related to Bug #21840: use twine instead of setup.py upload for PyPi uploads added
Actions