activate PIPENV_VENV_IN_PROJECT with --local

[kennethreitz]

No description provided.

[Enteleform]

Compimentary Feature Proposal

Replace the hardcoded ".venv" value with a dir parameter that defaults to ".venv"
 

Examples:

PIPENV_VENV_IN_PROJECT=false
C:\TEMP> pipenv install

>>> C:\Users\Enteleform\.virtualenvs\VENVS-SaQNVeuu

PIPENV_VENV_IN_PROJECT=true
C:\TEMP> pipenv install

or

C:\TEMP> pipenv install --local
C:\TEMP> pipenv install -l

>>> C:\TEMP\.venv

C:\TEMP> pipenv install --dir __env__
C:\TEMP> pipenv install -d __env__

>>> C:\TEMP\__env__

 

Exposing the parameter seems simple enough, although I'm not sure how it would affect commands like
pipenv install somepackage
or
pipenv shell

Ideally pipenv would automatically resolve the directory with the default command syntaxes, but as a user with strong filesystem preferences; even having to include the --dir switch on all commands would be better than nothing.

[GitShaffi]

Have created the below PR to fix this.
#3108

pipenv install --local
or
pipenv install -l

will now create the venv directory within the project.

[matteius]

I am thinking we would be better off adding a pipenv activate command at this point that activates whichever the appropriate project virtualenv is determined by the same logic as pipenv --venv