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
I think the insistence on .venv (with leading dot) is a bit too much. I get that the idea is to install in the project venv and not any old venv, but there should be a bit of give here.
Perhaps the heuristic should be:
'is $VIRTUAL_ENV a subdirectory of dirname pyproject.toml
rather than the current
'is $VIRTUAL_ENV equal to $(dirname pyproject.toml)/.venv
I think the insistence on
.venv
(with leading dot) is a bit too much. I get that the idea is to install in the project venv and not any old venv, but there should be a bit of give here.Perhaps the heuristic should be:
$VIRTUAL_ENV
a subdirectory ofdirname pyproject.toml
rather than the current
$VIRTUAL_ENV
equal to$(dirname pyproject.toml)/.venv
Also, note that
.venv
vsvenv
is a somewhat controversial choice, with a bunch of people/systems feeling strongly either way. (FWIW, personally I don't, but I'd rather not have to exhort people to rename their venvs.)The text was updated successfully, but these errors were encountered: