refactor: split py_venv binary vs lib rules#980
Conversation
|
9c55626 to
1b0356f
Compare
✨ Aspect Workflows Tasks📅 Fri Jun 26 19:55:08 UTC 2026 ✅ 14 successful tasks
⏱ Last updated Fri Jun 26 19:59:43 UTC 2026 · 📊 GitHub API quota 58/15,000 (0% used, resets in 42m) |
py_binary startup benchmark
sys.path quality
✅ No regression detected (PR is -0.2% vs HEAD main) |
Some tests that would have caught a regression in #980 🤷 ### Changes are visible to end-users: no ### Test plan - New test cases added
b6b60c4 to
d800794
Compare
Assemble each executable's private runtime venv in its owning rule rather than creating a configured sibling target. The sibling transition forced main-file resolution before configurable srcs were available and added a target for every py_binary and py_test. Keep physical sibling venv targets only for explicitly exposed layouts.
eab1f49 to
9ece534
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
9ece534 to
dea7beb
Compare
dea7beb to
9872c8e
Compare



This way if the
py_venvis not being exposed viapy_binary(expose_venv)it will be a simpler rule only exporting theVirtualenvInfoand runfiles, noRunEnvironmentInfoorDefaultInfo(files)Changes are visible to end-users: no
Test plan