migration to pyo3 0.21 new Bound
API
#410
Merged
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.
pyo3
0.21 is on the final stretch to release, with an initial beta expected in the next few days.This starts the migration to
pyo3
s newBound
API. This initial PR bumps thepyo3
version, enables thegil-refs
feature (to suppress most of the deprecation warnings) and adjust the rest to compile and pass the tests again.Note:
PyTypeInfo
needs to be updated tois_type_of_bound
now, because otherwisepyo3
s internals will not use the custom implementation, as found in PyO3/pyo3#3929I've prepared followups migrating different parts of the API in (hopefully) reviewable chunks. Generally I took a similar approach to
pyo3
itself, leaving old API around (for easy migrations) and adding deprecation warnings where necessary.I'll leave this as a draft until the beta release drops and rebase this than.