-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
pyenv launcher: introduce and export _PYENV_INSTALL_PREFIX #3334
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
Conversation
|
Not interested in this one ? |
|
I was just occupied by other things. In fact, I looked at this a few hours ago. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, could you check all instances of BASH_SOURCE usage? This is usually the sign that we're trying to detect the installation prefix. I saw one such place in pyenv---version.
|
Thanks for the feedbacks, will try to make the change in a few days |
|
I apologize for taking long to review. I looked at this soon after you made it, had doubts about it and thought that perhaps I can allocate time to make some own changes to address them myself. But about some of my changes, I wasn't sure, either, so it ultimately went nowhere. Should've probably started a discussion right away -- now all that my strategy achieved is waste 3 weeks. |
edb83c6 to
70747e2
Compare
Description
Add PYENV_INSTALL_PATH as an exposed variable by
pyenvcorresponding to the directory where pyenv is installedTests
Test updated to reflect the change