-
Notifications
You must be signed in to change notification settings - Fork 789
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
Update py03 from 0.20 to 0.21 #5566
Merged
Merged
Changes from 2 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
b5c9bb2
Update py03 from 0.20 to 0.21
Jefffrey 5f63906
Bump pyo3 in arrow-pyarrow-integration-testing
Jefffrey 7157f38
Merge branch 'master' into update-py03-0.21
Jefffrey cecc24a
Update pyarrow API to align with pyo3 0.21 changes
Jefffrey 646052b
Fix arrow-pyarrow-integration-testing clippy
Jefffrey 3a1956f
Minor
Jefffrey b1f5c49
Fix typo
Jefffrey 53b3b6b
Use PyBackedStr when extracting
Jefffrey 8a7c9be
Bump to pyo3 0.21.1
Jefffrey 3958759
Trigger
Jefffrey File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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'm not familiar with pyo3, so I was following the migration guide: https://pyo3.rs/v0.21.0/migration.html
Of particular note is:
So it seems they are moving away from
&PyAny
is my understanding. This raises a question of if the PyArrow API's should follow suit?e.g. here, introduce a new function that uses
Bound
?arrow-rs/arrow/src/pyarrow.rs
Line 141 in 5f63906
For now I've used
into_gil_ref()
to get around this deprecation process, but I don't think it's meant to be a permanent solution.I'll do some more reading, maybe it's been discussed in pyo3 before somewhere 🤔