CI Test failures. actions/setup-Python does not support Pythons 3.7-3.8 on the new Ubuntu 24.04 runners · Issue #1642 · tqdm/tqdm · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
run 3.7 and 3.8 on the old Ubuntu runners. A stop gap until the 22.04 ones are dropped
Use a different Python-version management tool in CI, e.g. uv or Pyenv. uv is where things are headed, and is what a lot of us would use locally anyway. This fix is nice and decently reproducible, but refactors the CI workflows.
Run the tests in a docker-containerised Github Action, using Python 3.7 and 3.8 images. This is future proof due to the Docker container version pinning, but does not replicate old Pythons on MacOS or Windows runners, and refactors the CI workflows.
replace actions/setup-Python with the backport, LizardByte/setup-python-action. Easiest change to make, simplest to review, but introduces a new external dependency.
Or support for Python 3.7 & 3.8 could be dropped, of course.
The text was updated successfully, but these errors were encountered:
Example tqdm action:
https://github.com/tqdm/tqdm/actions/runs/12440982004
Supported versions:
https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json
Various fixes could be possible, e.g.
Or support for Python 3.7 & 3.8 could be dropped, of course.
The text was updated successfully, but these errors were encountered: