Open Semnodime opened 4 months ago
This is expected behavior today. You are welcome to take on improving this logic to detect and prompt use to upgrade their virtualenv (which would be like invoking pipenv --rm
and pipenv sync
to recreate it.
This is expected behavior
The pipenv help suggests otherwise:
Usage Examples:
Create a new project using Python 3.7, specifically:
$ pipenv --python 3.7
After a environment has been created with pipenv --python 3.10
, pipenv --python 3.12
won't inform the user that a virtual environment does already exist and won't be upgraded. The command exits with return code 0
which does suggest every wen't without errors. No virtual environment has been created though, in contrast to its internal command description.
Issue description
pipenv install --python 3.12
Expected result
Actual result
Steps to replicate