-
Notifications
You must be signed in to change notification settings - Fork 175
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
Remove support for Python 3.8 #1290
Conversation
Pull Request Test Coverage Report for Build 11171426645Details
💛 - Coveralls |
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.
This lgtm and it looks like is ci passing with the correct python versions. Thanks for doing this.
@@ -1,9 +1,6 @@ | |||
queue_rules: | |||
- name: automerge | |||
conditions: | |||
- check-success=python3.8-x64 windows-latest |
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 need to push a PR to update this config with GitHub merge queues we don't need this, and we can only use mergify for automated backporting.
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.
Ditto. I actually quite like the GitHub queues, we could move some more expensive checks to the final merge instead of running them each time
This is our yearly Python version maintenance. 3.8 reached EOL. I will add the newly released 3.13 in a separate PR to test the wheel release etc.
I profited to update
black
,ruff
andmypy
as well.mypy
passes without any changes, but there were some minor differences withblack
andruff
.