Update to PyO3 Bound API#10
Merged
Merged
Conversation
Member
Author
This was referenced Mar 11, 2026
antoniobg
approved these changes
Mar 11, 2026
a3ee3f3 to
3c19e11
Compare
This was referenced Mar 13, 2026
3c19e11 to
3516571
Compare
Member
Author
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
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.

Motivation / Description
This pull request modernizes the PyO3 bindings to use the newer
Bound<'py, T>API instead of the legacyPy<T>API. The changes improve type safety and align with current PyO3 best practices by making Python object lifetimes more explicit.Changes introduced
build_cmd,build_meta_get,build_meta_set,build_meta_delete, andbuild_meta_arithmeticto use explicit lifetime parameters and returnBound<'py, PyBytes>instead ofPy<PyBytes>.into()conversions when creatingPyBytesobjects sincePyBytes::new()now directly returns the bound typeeqandskip_from_py_objectattributes toRequestFlagsandResponseFlagspyclass declarationsfrozenattribute toResponseFlagspyclass declaration__eq__method implementations from both flag classes since they're now handled automatically by theeqattributeto_bytesmethod inRequestFlagsto returnBound<'py, PyBytes>with explicit lifetime parameter