Actions
Bug #20723
closedStop running setup.py in our build+test infrastructure (will be deprecated by Oct 31st 2025)
Status:
Resolved
Priority:
Normal
Assigned To:
-
Target version:
-
Story points:
-
Release:
Release relationship:
Auto
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, …
Updated by Brett Smith over 2 years ago
- Related to Idea #20311: Update Python packages to build with PEP 517/518 added
Updated by Brett Smith over 2 years ago
- Related to Idea #21207: Decide and implement a modern way to run Python tests added
Updated by Brett Smith almost 2 years ago
- Related to Bug #21840: use twine instead of setup.py upload for PyPi uploads added
Updated by Lucas Di Pentima 11 months ago
- Subject changed from Stop running setup.py in our build+test infrastructure to Stop running setup.py in our build+test infrastructure (will be deprecated by Oct 31st 2025)
Today I noticed this message while reviewing #21362, so we have a deadline:
********************************************************************************
Please avoid running ``setup.py`` directly.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
By 2025-Oct-31, you need to update your project and remove deprecated calls
or your builds will no longer be supported.
See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
********************************************************************************
Updated by Brett Smith 9 months ago
- Target version deleted (
Development 2025-06-25) - Assigned To deleted (
Brett Smith)
Updated by Brett Smith 9 months ago
- Release changed from 79 to 28
- Status changed from New to In Progress
- Category deleted (
SDKs) - Project changed from Arvados to Arvados Epics
Updated by Brett Smith 8 months ago
- Related to Support #22436: Remove `arvados-server install`, `arvados-package` added
Updated by Brett Smith 8 months ago
- Related to Support #23012: Remove arvbox added
Updated by Brett Smith 5 months ago
- Status changed from In Progress to Resolved
Actions