-
Notifications
You must be signed in to change notification settings - Fork 1k
bump PyO3 to 0.26 #1901
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
bump PyO3 to 0.26 #1901
Conversation
ArthurZucker
left a comment
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.
LGTM
Is my understanding correct that with pyo3 0.26, building for py<3.14 will still work?
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
Yes, we still support python 3.7+. I'll fix the lint failures ASAP, probably later today. |
|
Lints fixed in 78af191 |
ngoldbaum
left a comment
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.
Thanks for taking this on!
ArthurZucker
left a comment
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.
Thanks a lot 🤗
First step towards getting tokenizers working on Python 3.14 free-threading.
This PR bumps PyO3 to 0.26. There are three major deprecations in this release, which cleaned up a bunch of PyO3 APIs to remove the "gil" association (which free-threading doesn't have). Each is carried out as a separate commit; in the final commit removing the
PyObjecttype alias forPy<PyAny>I happened upon a number of bits of code which had obvious simplifications. I applied those at the same time.