-
Notifications
You must be signed in to change notification settings - Fork 32
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
Conversation
End-to-end public repo |
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.
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.
d137312
to
f2b0b25
Compare
I've cheated and manually pushed the v2 to docker. So if the CI is green, I guess we should be all good. |
Tests are failing because we're matching on an exception and py3.11 exceptions are improved :) |
Coverage reportThe coverage rate went from None of the new lines are part of the tested code. Therefore, there is no coverage data about them. |
All good then ? |
Yes, looks good @ewjoachim |
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.