venv must be activated even when running via venv/bin/python -m uv
#1501
Labels
bug
Something isn't working
venv/bin/python -m uv
#1501
Seems likely related to #1374. I expect that even if usage outside of a venv is blocked, either universally by uv or because of
PIP_REQUIRE_VIRTUALENV=1
, activation should not be required as many people prefer tovenv/bin/python
instead of usingsource venv/bin/activate; python
.$ python3.11 -m venv venv
Above should work just as below does.
$ source venv/bin/activate
Just showing that below the same command works after the activation above.
The text was updated successfully, but these errors were encountered: