pyenv-virtualenv
pyenv-virtualenv copied to clipboard
pyenv
a pyenv plugin to manage virtualenv (a.k.a. python-virtualenv)
I have just noticed recently, that the above mentioned command does not switch to a virtual environment as before. Here how it looks like atm: ``` (base) art@HP:~$ python --version...
The construction `. "${BASH_SOURCE%/*}"/../libexec/pyenv-virtualenv-realpath`, on [line 9](https://github.com/pyenv/pyenv-virtualenv/blob/294f64f76b6b7fbf1a22a4ebba7710faa75c21f7/bin/pyenv-virtualenv-prefix#L9) of pyenv-virtualenv-prefix and [line 10](https://github.com/pyenv/pyenv-virtualenv/blob/294f64f76b6b7fbf1a22a4ebba7710faa75c21f7/bin/pyenv-virtualenvs#L10) of pyenv-virtualenvs results in an error if the script is symlinked into a directory on `PATH` (e.g. installed...
Tools such as pew, pipenv, and poetry all seem to support the creation of a subshell when entering a virtualenv. Although pyenv provides all the functionality that can be achieved...
I used to work with bash and installed bash without problem, but recently i change to zsh and i realize that i was using the system python version not from...
`pyenv-virtualenv` allows to create virtualenvs with names starting with a dot (e.g. `.dotfiles`), but those cannot be listed. This PR enables `dotglob` option when listing versions.
Apparently have some packages installed (virtualenv in particular) prevents the creation of a virtualenv. Im not sure if its expected that virtualenv/setuptools/pip at the user/system level should be honored instead...
Steps to reproduce: 1. pyenv virtualenv 3.6.8 .ve 2. pyenv virtualenvs Expected: two lines Observed: no lines Although `pyenv activate .ve` works, `pyenv deactivate` doesn't.
when i use pyenv virtualenv miniconda2-latest py27 i mean to create a env with python 2.7 same as miniconda2, but it create a env with python 3.7.1, is there something...
When I have pyenv-virtualenv installed:  The problem seems to disappear when I uninstall pyenv-virtualenv.
