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

Upgrade to Python 3.11 #217

Merged
merged 3 commits into from
Aug 4, 2023
Merged

Upgrade to Python 3.11 #217

merged 3 commits into from
Aug 4, 2023

Conversation

ewjoachim
Copy link
Member

@ewjoachim ewjoachim commented Jul 28, 2023

There are 2 commits. I think I'll need to isolate the 1st commit into its own branch, then merge it to let the CI create the v2 image, and then launch the CI for the rest of the PR and test everything. I wanted your opinion before doing anything too harsh @kieferro . Of course, this can wait until after the other ongoing PRs.

@github-actions
Copy link

End-to-end public repo
End-to-end private repo
If the tests fail, @ewjoachim will be added to the private repo

Copy link
Member

@kieferro kieferro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just by looking at it, that seems reasonable. And if we merge the first commit (which shouldn't really breaking anything). Then we can also see for the second one if all tests are passing.

@ewjoachim ewjoachim force-pushed the py311 branch 2 times, most recently from d137312 to f2b0b25 Compare July 30, 2023 15:32
@ewjoachim
Copy link
Member Author

I've cheated and manually pushed the v2 to docker. So if the CI is green, I guess we should be all good.

@ewjoachim
Copy link
Member Author

Tests are failing because we're matching on an exception and py3.11 exceptions are improved :)

@github-actions
Copy link

Coverage report

The coverage rate went from 100% to 100% ➡️
The branch rate is 100%.

None of the new lines are part of the tested code. Therefore, there is no coverage data about them.

@ewjoachim
Copy link
Member Author

All good then ?

@kieferro
Copy link
Member

kieferro commented Aug 4, 2023

Yes, looks good @ewjoachim

@ewjoachim ewjoachim merged commit 277f911 into v3 Aug 4, 2023
2 checks passed
@ewjoachim ewjoachim deleted the py311 branch August 4, 2023 15:17
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.

2 participants