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
Running a .venv target will create the virtual environment in the root of the repo, with the name .<target>.venv. The virtual environment is not inherently relocatable due to the relative paths inside of first_party.pth.
Describe the feature
Allow for the virtual environments to be created in the same directory as the rule is defined. The current default naming behavior is fine, but adding support for:
bazel run :target.venv env
to name the resulting virtual environment would be great!
Fund our work
Sponsor our open source work by donating a feature bounty
The text was updated successfully, but these errors were encountered:
The relative paths also cause issues if you want to package py_binary targets into tar balls using rules_pkg as the output file structure is different to when it is extracted in tree.
What is the current behavior?
Running a
.venv
target will create the virtual environment in the root of the repo, with the name.<target>.venv
. The virtual environment is not inherently relocatable due to the relative paths inside offirst_party.pth
.Describe the feature
Allow for the virtual environments to be created in the same directory as the rule is defined. The current default naming behavior is fine, but adding support for:
to name the resulting virtual environment would be great!
Fund our work
The text was updated successfully, but these errors were encountered: