Upgrading Pyo3 0.22 (with gil-refs) #504
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.
What does this PR do?
Upgrades to PyO3 0.22.
gil-refs
still required because I couldn't find a way to get access to the&[u8]
from the data pybuffer.Without gil-refs, the data is created in
pydata
which is dropped at the end of the loop, therefore the reference doesn't live long enough.I also tried changing everything around to use
FromPyObject
but it's not implemented for&[u8]
as it would requireFromPyObjectBound
which is a sealed trait.Additionally, the
SafetensorError
custom exception doesn't work withgil-refs
because it doesn't implement theHasPyGilRef
.Moving to just renaming
PyException
sort of seems to work without too much breaking change, although the exception is now the regular exception being effectively a catch all which is a breaking change.Fixes # (issue) or description of the problem this PR solves.