pipenv install --target /path/to/my/virtualenv/folder

Hi,

Could it be possible to create the virtualenv in the folder of our choice instead of ~/.local/share/virtualenvs/ ?

for example

pipenv install --target ~/fox_venv/projectA

which will create the venv in ~/fox_venv/projectA and not in ~/.local/share/virtualenvs/projectA-XdFl1243x

Regards

[uranusjr]

@kevinkjt2000 Yeah, our code base is so easy you never contributed anything.

[kevinkjt2000]

@uranusjr I acknowledge that you have a collaborator badge, but that is a rather sarcastic comment to make… I encourage you to encourage potential new-comers instead of steering the github comment section into frivolous, insulting conversations. If you would like more contributors; instead, try confirming or denying comments as they are made. Sarcasm is rather off-putting. I used the word seems, because of how unsure I was.

My comment pointed out that pipenv is capable of knowing what requirements are to be installed with lock -r and that pip is capable of installing that list of requirements. In my mind, pip seems to be the foundation behind how pipenv installs packages; however, as I am new to pipenv it only seems that way. I thought that in making the comment on an issue where it was stated that This is likely the closest we'll get to your current request for now. on late September last year, that perhaps someone more knowledgeable would re-visit and consider if it was easier after a few months of contributions and given that bash shell one-liner that I posted.