In order to have python use the current global pyenv version, you need to modify your PATH environment variable. See #2 under "Basic Github Checkout". Here's what it says to do the ZSH:
You could of course put that in the .zshrc instead of profile.
You need to make sure that the pyenv shims appear before the /usr/bin directory in the path. I'm not sure how the update-alternatives works with this, but I've never had an issue with pyenv with the shims at the front of the path. A call to
which python
should point to the pyenv shim, given you restarted the shell
👋 Hey there, I am Waylon Walker
I am a Husband, Father of two beautiful children, Senior Python Developer currently working in the Data Engineering platform space. I am a continuous learner, and sha
I put pyenv root right to the front of the $PATH and it was still going for system first. I ended up running update-alternatives --remove, and now pyenv has full control.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In order to have
pythonuse the current global pyenv version, you need to modify yourPATHenvironment variable. See #2 under "Basic Github Checkout". Here's what it says to do the ZSH:You could of course put that in the .zshrc instead of profile.
You need to make sure that the pyenv shims appear before the /usr/bin directory in the path. I'm not sure how the update-alternatives works with this, but I've never had an issue with pyenv with the shims at the front of the path. A call to
should point to the pyenv shim, given you restarted the shell
I put pyenv root right to the front of the $PATH and it was still going for system first. I ended up running update-alternatives --remove, and now pyenv has full control.