[go: nahoru, domu]

Skip to content
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

feature: Prepend To Path Option #213

Open
joeld1 opened this issue Mar 6, 2021 · 2 comments
Open

feature: Prepend To Path Option #213

joeld1 opened this issue Mar 6, 2021 · 2 comments
Assignees

Comments

@joeld1
Copy link
joeld1 commented Mar 6, 2021

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!

@joeld1 joeld1 changed the title Prepend To Path Option Prepend To Path Option :Feature Mar 6, 2021
@joeld1 joeld1 changed the title Prepend To Path Option :Feature Prepend To Path Option Mar 6, 2021
@joeld1 joeld1 changed the title Prepend To Path Option feature: Prepend To Path Option Mar 6, 2021
@kirankotari
Copy link
Member

@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.

@kirankotari kirankotari self-assigned this Mar 18, 2021
@papercuptech
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants