Open
Description
What happened?
In 1.4.0 having a py_venv target with the name venv in the workspace root build file would create a virtual environment $BUILD_WORKING_DIRECTORY/.venv, which was convenient because it would be found automatically by IDEs. In 1.6.0 it creates $BUILD_WORKING_DIRECTORY/.+venv instead. Would it be possible to bring back the original behavior?
It looks like #589 meant to restore the original name mangling, but this seems to be another case.
Version
Development (host) and target OS/architectures:
Output of bazel --version:
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:
Language(s) and/or frameworks involved:
How to reproduce
Any other information?
No response