PIPENV_VENV_IN_PROJECT=true should be default behavior

Is there a reason why pipenv is poluting ~ with virtualenvs by default? To me it doesn’t make any sense. If the specific virtualenv is associated with specific project than why store it somewhere deep inside your ~ and not in the project’s folder?

[olegantonyan]

That’s weird

As a note, now that the original “put virtualenv in project dir” default behavior has been changed (sadly), the Pipenv README should be changed. It shows a virtualenv getting created in the project dir.

But why? I don’t understand why would anyone change good design to bad

[uranusjr]

@olegantonyan I don’t think either design is bad (or good). There is wild-spread usage of tools using a centralised virualenv storage, such as virtualenvwrapper, Anaconda’s virtualenv support, and pyenv-virtualenv. I’d guess none of their users think it is a bad idea. It is subjective.

(Disclaimer: I do prefer the virtualenv-beside-project approach, and set PIPENV_VENV_IN_PROJECT on my machine. I just don’t think either is objectively superior, at least not much.)