PEEP proposal for venv location

[gsemet]

Following #796, my humble proposal

[kennethreitz]

this is out of scope.

[yuwash]

I indeed don’t see a necessity for PIPENV_INSTALL_VENV_DIR=custom/path or the corresponding --venv-dir, but the option --venv is basically the same as calling pipenv with PIPENV_VENV_IN_PROJECT=1, so I think that’s not a vastly new thing to the project. A short command-line argument is easier to use when it’s only needed on setup.

It might be better to name it --in-project though.

[gsemet]

Now I would recommend a setting inside pipenv.toml that can be overridden by parameter.

It is always messy to let all users know they have to set this variable or create a .venv folder prior to do the pipenv install.

I use poetry now at least we can commit a setting in poetry.toml