Trying pipenv for the first time:
> cd ~
> mkdir foo
> cd foo
> pipenv install
> pipenv --venv
> [/Users/richardlyon/.venv]
> cd ..
> mkdir bar
> cd bar
> pipenv install
> pipenv --venv
> [/Users/richardlyon/.venv]
I cannot relate this to my reading of the pipenv manual, which suggests that a separate virtual environment should created for each directory in which pipenv is invoked. Nor can I see the advantage of this arrangement.
Could anyone shed any light? Thank you.
OK. Looks like fiddling around had created file Pipfile in the root which was making pipenv treat root as an existing virtual environment. Deleting it fixed the problem.
Leaving this here in case anyone else (new) comes across this - it didn't show up as an issue in a web search.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With