You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if it's possible to add a prepend to path option, or update the docs to prepend the pyenv path?
Just wondering because I also have Anaconda on my computer, and it usually prepends to path whenever I do fresh installs on a computer. This is annoying because I have to constantly rearrange the path so that it first looks for Python within the pyenv folder instead of Anaconda.
I know where to look when this happens, but this small change or option will be useful for new users that wonder why they can't run any newly installed (via Pyenv) Python installations 😄 .
Anyhow, just a small suggestion, and thank you for developing this package - it's awesome!
The text was updated successfully, but these errors were encountered:
joeld1
changed the title
Prepend To Path Option
Prepend To Path Option :Feature
Mar 6, 2021
joeld1
changed the title
Prepend To Path Option :Feature
Prepend To Path Option
Mar 6, 2021
joeld1
changed the title
Prepend To Path Option
feature: Prepend To Path Option
Mar 6, 2021
@joeld1 I have following PR #140 which I haven't tested that might solve your need. After testing that I will merge to the master branch but it takes time for me.
@joeld1 Upon review of Anaconda install docs here and here it seems the general recommendation is not to alter PATH as part of installing Anaconda. I also believe if one were to install python directly (no pyenv anywhere), and then install Anaconda such that the installer alters PATH, your same circumstance would arise. All this implies to me that fixing the issue should be done outside of pyenv.
Having said that, PR #140 will allow you to run pyenv exec cmd which creates a new command shell where PATH has been prefixed with paths to pyenv's active python version, but the PATH alteration lives only within that new command shell, and does not alter PATH at the system/user level (i.e. "permanently"), meaning each time you open a new command shell terminal, you would then need to run pyenv exec cmd.
I'm wondering if it's possible to add a prepend to path option, or update the docs to prepend the pyenv path?
Just wondering because I also have Anaconda on my computer, and it usually prepends to path whenever I do fresh installs on a computer. This is annoying because I have to constantly rearrange the path so that it first looks for Python within the pyenv folder instead of Anaconda.
I know where to look when this happens, but this small change or option will be useful for new users that wonder why they can't run any newly installed (via Pyenv) Python installations 😄 .
Anyhow, just a small suggestion, and thank you for developing this package - it's awesome!
The text was updated successfully, but these errors were encountered: