Closed iddan closed 6 years ago
I feel like PIPENV_VENV_IN_PROJECT is a second class citizen in the CLI while it is a common solution in other tools (like PyCharm) and seem like more of an option than an actual environment variable.
PIPENV_VENV_IN_PROJECT
I'd like to propose the syntax:
pipenv --python 3 --in-project;
pipenv install --in-project;
Instead of:
export PIPENV_VENV_IN_PROJECT=1; pipenv --python 3;
export PIPENV_VENV_IN_PROJECT=1; pipenv install;
Another way to solve this issue is making it the default and managing hidden virtual envs with magic.
This would belong to pipenv's issue tracker: https://github.com/pypa/pipenv/issues
This project is for discussing the changes to and standardization of the Pipfile format.
Oops, my mistake!
I feel like
PIPENV_VENV_IN_PROJECT
is a second class citizen in the CLI while it is a common solution in other tools (like PyCharm) and seem like more of an option than an actual environment variable.I'd like to propose the syntax:
Instead of:
Another way to solve this issue is making it the default and managing hidden virtual envs with magic.