Re-vendor pyo3 at the v0.23.4 commit #1421
Merged
Conversation
This file contains 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
agola11
approved these changes
Jan 15, 2025
obi1kenobi
force-pushed
the
pg/update_vendored_pyo3
branch
from
7829342 to
1c02143
Compare
obi1kenobi
changed the title
obi1kenobi
changed the title
obi1kenobi
added a commit
that referenced
this pull request
Jan 15, 2025
`orjson` still uses non-published functionality in `pyo3`, so we have to keep it vendored. Update our vendored `pyo3` to v0.23.4, to pick up the soundness fixes in v0.23.3.
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.
orjsonstill uses non-published functionality inpyo3, so we have to keep it vendored.Update our vendored
pyo3to v0.23.4, to pick up the soundness fixes in v0.23.3.