Skip to content

Conversation

@rockandska
Copy link
Contributor

Description

Add PYENV_INSTALL_PATH as an exposed variable by pyenv corresponding to the directory where pyenv is installed

Tests

Test updated to reflect the change

@rockandska rockandska requested review from a team as code owners September 18, 2025 15:35
@rockandska
Copy link
Contributor Author

Not interested in this one ?
Should I close it ?

@native-api
Copy link
Member

I was just occupied by other things. In fact, I looked at this a few hours ago.

Copy link
Member

@native-api native-api left a 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.

@rockandska
Copy link
Contributor Author

Thanks for the feedbacks, will try to make the change in a few days

@native-api
Copy link
Member

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.

@native-api native-api merged commit 2c38423 into pyenv:master Dec 24, 2025
20 checks passed
@native-api native-api changed the title PYENV_INSTALL_PATH created and exported pyenv launcher: introduce and export _PYENV_INSTALL_PREFIX Dec 24, 2025
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

Successfully merging this pull request may close these issues.

2 participants