Open limsammy opened 2 years ago
@limsammy First of all, thank you for your kind words and the submitted issue!
Actually, I had a pretty outdated version of pyenv on my machine. I have updated it to the latest (2.0.6-7) and checked if I can reproduce the issue. Unfortunately, on my machine everything still works fine.
However, I've tried to investigate what can be the problem in your case. First of all, it seems that virtualenv plugin is not working correctly for some setups after upgrading to pyenv v2 (pyenv corresponding issue and pyenv-virtualenv issue). Try to use the workarounds provided in these issues.
Also, could you please check if the command pyenv versions
(without additional flags) work fine on your setup?
I also ran into this issue - escaping the expansion of the list on line 107 did the trick for me, I'm unsure if there should be other escapes on the other quoted expansions so replying here instead of submitting a PR, leaving that up to you @zyrikby - fantastic work!
original:
if ! elementIn "${argument}" "${pyenvs_to_update[@]}"; then
escaped:
if ! elementIn "${argument}" "\${pyenvs_to_update[@]}"; then
@sunflailOOH Do you also use Mac?
First of all, this is an awesome plugin.
To the issue:
I cannot seem to specify a specific virtualenv. I have many virtualenv's managed with pyenv so I cannot test the
--all
option to see if it is an issue with something in my global environment.Errors:
Worth noting calling the command with no arguments returns a similar error:
Also see number 5 below using full path as arg instead, outputs different error
Reproducing:
--help
argAgain, this plugin looks incredible, and would love to help contribute if this is some sort of environment-specific issue (zsh, osx, etc.)
EDIT: Also from your blog post I have used
pyenv versions --bare --skip-aliases
and attempted to use that output as an arg, same error.