Luis Marsano e0a1e9b35c support newer conda ... pyenv-virtualenvs could not list conda environments & pyenv shell would only activate the base conda environment the conda detection criteria of testing the presence of `conda` or `activate` files under `$(pyenv root)/versions/$version/bin` appears to be the culprit, since newer environments no longer include these files: those files reside in the base conda environment - add detection criteria of `$(pyenv root)/versions/$version/conda-meta` - compute the real prefix to the base environment from `realpath $(realpath $(pyenv root)/versions/$version)/../..` - to allow that, enhance substitute `realpath` in `pyenv-virtualenvs` to reduce relative paths `.` & `..`, and factor that code out to a file under `libexec` for reuse - hook `which` to locate conda from the real prefix		2018-11-21 22:00:56 -05:00
..
pyenv-activate	Fix completion of pyenv activate (fixes #15)	2014-02-03 14:49:47 +09:00
pyenv-deactivate	Display error if pyenv activate was invoked as a command	2014-01-25 19:14:58 +09:00
pyenv-sh-activate	support newer conda	2018-11-21 22:00:56 -05:00
pyenv-sh-deactivate	support newer conda	2018-11-21 22:00:56 -05:00
pyenv-virtualenv	v1.1.3	2018-05-24 12:28:04 +00:00
pyenv-virtualenv-delete	Add workaround for rywyo/anyenv	2015-12-04 00:43:03 +00:00
pyenv-virtualenv-init	fish: use "set -gx" instead of "setenv" (#218)	2017-06-08 21:52:57 +02:00
pyenv-virtualenv-prefix	support newer conda	2018-11-21 22:00:56 -05:00
pyenv-virtualenvs	support newer conda	2018-11-21 22:00:56 -05:00