Bump pyo3 to 0.29 - #77
Merged
Merged
Conversation
1 task
|
It would be nice if the upper bound was higher so this crate didn't need a release every time there's a PyO3 release. But I understand the risk of breakage. |
Owner
|
Indeed, it feels like a not optimal solution, but pyo3 has a history of breaking API between versions, unfortunately - so it's a trade between a friction if users want to upgrade their pyo3 and need to poke me and wait, and the risk of breaking downstream users all over the place without them doing anything much. |
Owner
|
Released as 0.13.4. |
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.
Fixes #76