Bump pyo3: 0.25.1 -> 0.28.3#111
Merged
Merged
Conversation
ReinierMaas
approved these changes
Jul 3, 2026
ReinierMaas
left a comment
ReinierMaas
left a comment
Contributor
There was a problem hiding this comment.
To me this makes sense but I haven't written much pyo3 code.
jerbaroo
force-pushed
the
jerbaroo-36-upgrade-pyo3
branch
from
89795ff to
a49a935
Compare
Contributor
Author
|
@OpsBotPrime merge |
Approved-by: jerbaroo Priority: Normal Auto-deploy: false
Contributor
|
Rebased as 002dfd6, waiting for CI … |
Contributor
|
CI job 🟡 started. |
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
3 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.
This PR includes 3 commits. For each commit simply bumped the minor version of pyo3 then addressed the compiler deprecation warnings and errors and ensured that the test-suite still passed.
@Qqwy while a ✅ from the compiler and test-suite are good signs, I'm not entirely confident whether the code in
async_utilis what we want, would suggest review keenly 🙏🏻