-
Notifications
You must be signed in to change notification settings - Fork 91
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
[FIX] github pre-commit action: pin python version to 3.11 #214
Conversation
Thanks ! Some test are failing. Could you take a look ? |
Python 2.7 issue. Related PR #199 |
@@ -13,4 +13,6 @@ jobs: | |||
steps: | |||
- uses: actions/checkout@v3 | |||
- uses: actions/setup-python@v2 | |||
with: | |||
python-version: "3.11" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this one shouldn't be pinpointed. The problem is in pre-commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this one shouldn't be pinpointed. The problem is in pre-commit.
I think otherwise. Github action should not behave differently when suddenly other python version is used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem pinpointing this is that when GitHub removes this version in the future, we will have a red CI, and meanwhile lots of version have passed, and we lost the opportunity to improve during it. It's not a big deal though, as this is only the CI for this repo, and the effort to change it is not too much.
The template is other beast, as it propagates to each OCA repo, but pinpointing is right now the only option (or wait till pre-commit fixes whatever problem it is), and maybe we will need to raise any library version as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we must pin the python version for pre-commit, just like we pin it for running tests.
Otherwise we hit this kind of issue every time GitHub upgrades its default python.
My suggestion would be to use the same python version as for the tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure what you want to say here. Can you do a suggestion if still on time?
Being tested in OCA/sale-workflow#2748 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not available today, I'll see what I can do this weekend. In the meantime if any board member or core maintainer wants to do the mass update, feel totally free (using oca-copier-update in maintainer-tools). |
Version 14 is also affected. |
Set python versio to 3.11 referencing to this OCA/oca-addons-repo-template#214
Set python versio to 3.11 referencing to this OCA/oca-addons-repo-template#214
Set python versio to 3.11 referencing to this OCA/oca-addons-repo-template#214
Thank you, Stéphane. |
Recently I had problems with passing pre-commit, since github action started to use Python 3.12
When running pre-commit action on 3.12 you get following errors:
Pinning to 3.11 fixes errors above.