Reid D McKenzie
Reid D McKenzie
Yep, this and ripping out the WORKSPACE file is the basis of the 2.0 I want to cut.
I think this is best solved with documentation. We don't want to make choices of dependencies on behalf of our users, since that leads to us becoming a pinch point...
It's a regression yes but not really a bug. `venv_link` gives you a link to the venv defined by your Bazel target and as will be used by the binary...
I'd accept a PR to add a config setting flag and make what the `.venv` target of the reference `py_binary` macro does selectable. My general preference continues to be eliminating...