chore(release): support explicit Python in RC verifier#2740
Open
manuzhang wants to merge 1 commit into
Open
Conversation
manuzhang
changed the title
Co-authored-by: Codex <codex@openai.com>
manuzhang
force-pushed
the
codex/release-verifier-python-dylib
branch
from
b3bfcd6 to
26a8e3d
Compare
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
1 participant
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.
Summary
--python_bin/--python-bintodev/release/verify_rc.sh.PYO3_PYTHONandUV_PYTHONfor Rust workspace and pyiceberg-core verification steps.Why
During 0.10.0 RC verification, Python-linked Rust test discovery could fail on macOS when the active Conda Python did not provide a shared
libpythondylib. The release artifacts were valid, but the verifier needed a supported way to point PyO3 and uv/maturin at a Python.org or Homebrew interpreter with a shared library.Co-authored-by: @codex