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
Currently venv creation is tied to the terminal py_binary or py_test.
Under bazel this is fine and what we want, but for IDEs the user likely wants to create a venv for all the targets in their project, ie, all the test and binary targets in a given scope, or at the very least all the test targets so the IDE can run them.
This will lead to potential differences between testing under bazel and testing via the IDE as tests may have access to dependencies in the IDE that they wouldn't have under bazel.
The text was updated successfully, but these errors were encountered:
Currently venv creation is tied to the terminal
py_binary
orpy_test
.Under bazel this is fine and what we want, but for IDEs the user likely wants to create a venv for all the targets in their project, ie, all the test and binary targets in a given scope, or at the very least all the test targets so the IDE can run them.
This will lead to potential differences between testing under bazel and testing via the IDE as tests may have access to dependencies in the IDE that they wouldn't have under bazel.
The text was updated successfully, but these errors were encountered: