#320 should be simpler if we decide to drop Python 3.6 support first #333 (comment)
This might actually be reasonable, as ReFrame 4.10.0 only supports Python 3.10 onwards. We discussed this in the test-suite sync meeting, and we all agreed.
I think this means we can go to a pyproject.toml-only setup. And we can drop all of the complexity from here
|
if python_version >= (3, 8) and current_setuptools_version >= pkg_resources.parse_version("61.0.0"): |
Should update
|
python-version: ['3.7', '3.8', '3.9', '3.10', '3.11'] |
, also add newer versions of python
Switch
to 24.04
We'll also have to make changes to CI/run_reframe.sh so that it can either pick up on newer python versions (even if they are not the default), or install a newer python with UV.
We'll try to jump to Python 3.8 onwards for now, see if that's sufficient to get rid of all our current complexity.
#320 should be simpler if we decide to drop Python 3.6 support first #333 (comment)
This might actually be reasonable, as ReFrame 4.10.0 only supports Python 3.10 onwards. We discussed this in the test-suite sync meeting, and we all agreed.
I think this means we can go to a
pyproject.toml-only setup. And we can drop all of the complexity from heretest-suite/setup.py
Line 24 in 209966b
Should update
test-suite/.github/workflows/automatic_versioning.yml
Line 11 in 209966b
Switch
test-suite/.github/workflows/automatic_versioning.yml
Line 7 in 209966b
We'll also have to make changes to
CI/run_reframe.shso that it can either pick up on newer python versions (even if they are not the default), or install a newer python with UV.We'll try to jump to Python 3.8 onwards for now, see if that's sufficient to get rid of all our current complexity.