You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Audit vendored extensions by package, not by abi3 tag
abi3 answers only half the question. protobuf-py-ext's wheel is
cp310-abi3-manylinux_2_17_x86_64: stable across CPython versions, and still
unable to load on Windows, macOS or ARM. Letting the tag alone grant a pass
would have waved through a future dependency whose extension is required,
breaking every platform except the Linux builder, with no check firing.
What makes an extension safe to vendor into a single cross-platform artifact is
the package treating it as optional. Both of these do, so list them and fail on
anything else: protobuf-py catches the failed import and falls back to pure
Python, so its extension is kept for the platform it does load on, and nothing
imports playhouse at all, so its 2 MB are dropped.
Refuse a line in uv's export that is neither a comment, a --hash continuation,
nor an option, instead of skipping it. Options add no distribution and stay
skipped; an editable would, and silently leaves it outside every later check.
Both found by Codex reviewing the branch.
0 commit comments