-
Notifications
You must be signed in to change notification settings - Fork 17
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
Support PyO3 0.23 #98
Labels
enhancement
New feature or request
Comments
Thanks for the issue / analysis! Definitely appreciated. I'm not sure I'll have any time to look into this for the next few weeks, so a PR (from anyone) is definitely welcome, otherwise hopefully will have a look at some point. |
I'm planning to take a look at this. |
That would be amazing, thanks Nathan! |
I created #100, I'll follow up once 0.23 is finalized. |
Fixed by #100 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PyO3 0.23 is coming out soon (hopefully this week).
Supporting it should allow supporting the free-threaded build of Python 3.13 as well.
Here's the compiler error I get if I patch
Cargo.toml
to point at a local copy of the PyO3 repo with themain
branch checked out:It looks like almost all of the errors are related to the introduction of
IntoPyObject
and the removal of the gil-refs API so hopefully most of these will be straightforward to fix. I don't see anything related to the newSync
trait bound 0.23 adds to pyclasses, so that's good.The text was updated successfully, but these errors were encountered: