Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update CI python version from 3.6 to 3.11 #5025

Merged

Conversation

I-Al-Istannen
Copy link
Collaborator

@I-Al-Istannen I-Al-Istannen commented Nov 26, 2022

Github recently updated their ubuntu-latest image to 22.04. This broke setup-python as it no python 3.6 tarball is provided (actions/setup-python#544).

This PR fixes the issue by just updating the CI to use python 3.9. It does not adjust the ci scripts to take advantage of possible new python features introduced since then.

This breakage is responsible for the current red master (as the PR run was executed before the Github runner change but the master action ran after it) and unblocks some PRs.


I also needed to update commonmark. Note that commonmark is deprecated for over a year now: readthedocs/commonmark.py#308. We might to want migrate away from it in a future PR, though we don't really need to. The source code we analyze is benign so security isn't really an issue and the featureset is enough for us.

@I-Al-Istannen I-Al-Istannen changed the title wip: chore: Update CI python version from 3.6 to 3.9 review: chore: Update CI python version from 3.6 to 3.9 Nov 26, 2022
@MartinWitt
Copy link
Collaborator

Is there a reason we don't upgrade to the newest python version? I'm kind of out of the loop for python and if the break APIs we use.

@I-Al-Istannen
Copy link
Collaborator Author

I-Al-Istannen commented Nov 26, 2022

I consider the python version in the CI some kind of "we support at least Version X" guarantee (as we see breakages directly in our CI). According to repology, a few are still on 3.9: https://repology.org/project/python/versions. Our python files are small and simple, upgrading for us should be basically free.

I'm fine with 3.11 as well.

@I-Al-Istannen I-Al-Istannen changed the title review: chore: Update CI python version from 3.6 to 3.9 review: chore: Update CI python version from 3.6 to 3.11 Nov 26, 2022
@MartinWitt MartinWitt changed the title review: chore: Update CI python version from 3.6 to 3.11 chore: Update CI python version from 3.6 to 3.11 Nov 28, 2022
@MartinWitt MartinWitt merged commit f88030f into INRIA:master Nov 28, 2022
@MartinWitt
Copy link
Collaborator

Thanks @I-Al-Istannen

@I-Al-Istannen I-Al-Istannen deleted the chore/upgrade-ci-python-version branch November 28, 2022 18:18
@slarse
Copy link
Collaborator

slarse commented Nov 29, 2022

We only use Python for scripts so we hardly need to care about... Anything. If it runs, it runs. There are a lot of breaking changes between 3.6 and 3.11 (especially when it comes to third party packages), but again, if our CI runs we're good :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants