-
Notifications
You must be signed in to change notification settings - Fork 48
upgrading to support python 3.14 #271
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
base: main
Are you sure you want to change the base?
upgrading to support python 3.14 #271
Conversation
| - {name: 'manylinux', py_suffix: ''} | ||
| - {name: 'manylinux_musl', py_suffix: '-alpine'} | ||
| python: | ||
| - {version: '3.13', spec: 'cp313-cp313'} |
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 you can remove the tests for 3.13 because the current CI workflow for PRs only validate the latest available release.
| All the same features are exposed through the Python interface. | ||
| Currently, the supported Python versions are 3.7, 3.8, 3.9 and 3.10. | ||
| Currently, the supported Python versions are 3.7, 3.8, 3.9, 3.10, 3.11, 3.12, 3.13, and 3.14. |
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.
| Currently, the supported Python versions are 3.7, 3.8, 3.9, 3.10, 3.11, 3.12, 3.13, and 3.14. | |
| Currently, the supported Python versions are 3.9, 3.10, 3.11, 3.12, 3.13, and 3.14. |
|
Hi |
|
I will prepare the next python release after the cpp release 4.0.0 is available, if this PR is not updated then, I will take over it. |
Motivation
Add support for Python 3.14 to keep the client up-to-date with the latest Python releases.
Modifications
Verifying this change
Documentation