chore: update pyo3 dependency to 0.29#10134
Merged
Merged
Conversation
Bump pyo3 from 0.26 to 0.29 in arrow-pyarrow, arrow-pyarrow-testing, and arrow-pyarrow-integration-testing. Adapt to pyo3 0.29 API changes in arrow-pyarrow: - `Bound::downcast` -> `cast` - `PyCapsule::reference`/`pointer` removed -> `pointer_checked` - `CapsuleName::to_str` removed -> `as_cstr().to_str()` - `FromPyObject` now takes two lifetimes with an associated `Error` type and an `extract(Borrowed)` method Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
timsaucer
force-pushed
the
feat/pyo3-0.29
branch
from
02e38ec to
26ca545
Compare
cargo install cargo-msrv resolves an unpinned transitive aws-runtime dependency that fails to compile (E0282 type inference error), breaking the MSRV job on all branches. --locked uses cargo-msrv's own pinned Cargo.lock, which compiles cleanly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
timsaucer
commented
Jun 12, 2026
Comment on lines
+121
to
+123
| # --locked uses cargo-msrv's pinned Cargo.lock; without it an unpinned transitive | ||
| # dep (aws-runtime) resolves to a version that fails to compile (E0282) | ||
| run: if which cargo-msrv ; then echo "using existing cargo-msrv binary" ; else cargo install cargo-msrv --locked ; fi |
Member
Author
There was a problem hiding this comment.
This is a drive by change to using the locked version to resolve this CI failure: https://github.com/apache/arrow-rs/actions/runs/27400807826/job/80978193449
timsaucer
changed the title
timsaucer
changed the title
Jefffrey
approved these changes
Jun 13, 2026
Contributor
|
thanks for the fix to msrv too |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Which issue does this PR close?
None, just a dependency update.
Rationale for this change
pyo3 has security vulnerability: https://rustsec.org/advisories/RUSTSEC-2026-0176.html
This PR updates to 0.29 to resolve this vulnerability.
What changes are included in this PR?
Update all crates that use the pyo3 dependency to 0.29
Are these changes tested?
Updated and run against existing integration test suite.
Are there any user-facing changes?
No