-
Notifications
You must be signed in to change notification settings - Fork 436
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
bash: pyenv: command not found and how to solve it #103
Comments
Same error under Funtoo-Linux. Using the above fix, the error message goes away, when starting a new interactive shell (terminal). However, when running
still errors out. |
For Ubuntu OS, you can face the same problem. So, after installing the dependencies and pyenv in terminal just type the following commands one by one : |
I have done the steps provided by @goncaloperes . but still I am getting below error. I am using Centos 7. Can anyone face this issue ? [centos@localhost ~]$ exec "$SHELL" |
Pyenv installer gives you instructions about what you need to do next (install Pyenv into the shell, it can't do that automatically due to many different shell setups out there). Note that in version 2.0.0, the required shell setup has changed, so please heed the instructions (so that you don't waste your and our time reporting bugs that are not there). |
The problem is not solved, still getting the same error. |
on RL8, a note to myself or other. After I exited out of 2nd bash spawn of 1st bash. the installer script works.
|
I hope both sides of your pillow are cold tonight :) |
If you have downloaded pyenv to your home directory, all you have to do is add |
If you are on a mac for example and use zsh use this:
|
In CentOS 7, I ran
$ curl https://pyenv.run | bash
and then
$ exec $SHELL
However when trying to see if I had pyenv installed by updating it
pyenv update
I was getting the error
Solution (found here)
It turns out the pyenv path wasn't exported to .bashrc. It can be done by executing the following commands in terminal:
Then restart the shell
exec "$SHELL"
The text was updated successfully, but these errors were encountered: