-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin doesn't work with pyenv >= 2.3.10 #3
Comments
Hi. I’m no longer using pyenv, so it’s unlikely I’ll get to fix this. I’d be happy to accept a pr though … |
Thanks, that makes sense. Since my use case for pyenv is quite limited actually, I think I'll just work around it by pinning pyenv to an older version... |
I attempted to fix this, but not being much of a bash programmer I was unable to reproduce the previous behaviour. I have created an alternative that allows you to append a suffix to the version name: https://github.com/AdrianDAlessandro/pyenv-suffix To quickly explain the bug, if it helps fix this plugin... This plugin sets the Instead of working out how to pattern-match strings in bash to replace the whole version name at the tail of |
Another alternative is directly invoking |
For work pyenv-alias on pyenv 2.3.25 patch line 9 etc/pyenv.d/install/alias.bash: |
@igor-buzzoola any chance you can make a PR? |
It does work but will be the same as the forked one here: |
I think we may can make it simpler to read and probably easier to add more functions later.
|
Providing a suffix instead of a full name has been suggested in pyenv/pyenv#2810 and we're considering adding that into the base product due to apparent considerable demand for the alternate name feature. Evereyone is welcome to provide feedback on that. |
Hi! I'm curious as to the state of this. It looks like a reasonable fix is in @AdrianDAlessandro's fork. Does it simply need to be contributed here @s1341? |
Or perhaps the recommendation is to switch to |
When using pyenv 2.3.10 or later, specifying the VERSION_ALIAS seems to have no effect whatsoever.
I suspect that this change (pyenv/pyenv#2568) broke the version aliasing. I also verified that the plugin works correctly with pyenv 2.3.9.
The text was updated successfully, but these errors were encountered: