-
-
Notifications
You must be signed in to change notification settings - Fork 428
Description
pyenv-virtualenv not auto-resolve python version like pyenv can (for example, now, pyenv install 3.10 will install current latest 3.10.8)
https://github.com/pyenv/pyenv#prefix-auto-resolution
Command pyenv virtualenv 3.10 venv will create folder $PYENV_ROOT/versions/3.10/envs/venv instead of expected $PYENV_ROOT/versions/3.10.8/envs/venv
This also will break pyenv auto-resolve option, because even after delete virtual environment folder, $PYENV_ROOT/versions/3.10 will exist
Related pyenv issue: pyenv/pyenv#2533
NB: Also, I've faced fork-bomb problem somehow with this, when delete one of environments, caused by pyenv sh-activate in eval "$(pyenv virtualenv-init -)", but I didn't investigate this deeply, just completely remove $PYENV_ROOT and recreate it.
Prerequisite
- Make sure your problem is not listed in the common build problems.
- Make sure no duplicated issue has already been reported in the pyenv-virtualenv issues. You should look in closed issues, too.
- Make sure you are not asking us to help solving your specific issue.
- GitHub issues is opened mainly for development purposes. If you want to ask someone to help solving your problem, go to some community site like Gitter, StackOverflow, etc.
- Make sure your problem is not derived from packaging (e.g. Homebrew).
- Please refer to the package documentation for the installation issues, etc.
- Make sure your problem is not derived from other plugins.
- This repository is maintaining the
pyenv-virtualenvplugin only. Please refrain from reporting issues of other plugins here.
- This repository is maintaining the
Description
- Platform information: openSUSE Tumbleweed
- OS architecture (e.g. amd64): amd64
- pyenv version: 2.3.6
- pyenv-virtualenv version: 1.1.5
- Python version: 2.7.18, 3.10.8
- virtualenv version (if installed): none