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
`py_venv` contains relative `.pth` entries and symlinks that leave the
venv for source files and wheels in the target's runfiles tree. A
workspace symlink to only the venv changes their lexical base, so both
CPython and IDEs can resolve those paths outside the declared runfiles
layout.
Make `py_venv_link` link the complete directory-based runfiles tree and
print the nested venv path for IDE and shell configuration. This
preserves the generated venv layout, keeps `.pth` entries declarative,
and avoids either rewriting startup paths or adding a recursive
runfiles backedge.
Manifest-only launches cannot expose a directory and fail explicitly.
Windows therefore requires Bazel runfiles trees. The launcher must also
prefer a valid runfiles directory when Bazel supplies both sources; that
behavior is implemented by
tamird/hermetic-launcher@45d9b79.
0 commit comments