native-api
native-api
> > I also have a question closely linked to this issue. I recently created a pyenv plugin called [pyenv-link](https://github.com/real-yfprojects/pyenv-link). I would like to see it being listed in the...
> Though this policy could be stated somewhere in the Wiki to avoid future confusion. And how would one find it? Only if it's on the front page... I think...
Without the required diagnostic information as per the issue tempalte, we cannot diagnose an issue.
http://pyenv.run works as expected: ``` $ curl pyenv.run #!/bin/bash # # Usage: curl https://pyenv.run | bash # # For more info, visit: https://github.com/pyenv/pyenv-installer # index_main() { set -e curl -s...
Can't reproduce now.
Please update the PR for the tests to pass
Looking at https://github.com/pypa/virtualenv/blob/main/src/virtualenv/activation/bash/activate.sh , there's no deprecation, not to mention, removal of the prompt changing in sight. Lacking any response from @yyuu, my guess is: _Pyenv-virtualenv makes virtualenvs behave like...
> Pyenv-virtualenv makes virtualenvs behave like regular installations. The prompt changing removal was intended to erase the difference even further. In which case, we can as well go the other...
@albdv If it's set to be global(ly selected), it's not supposed to be deactivating, ever. Why would it? You deactivate it, but then Pyenv-Virtualenv sees that it's the selected version...
If you need something else, you need to either unset it as the global version, or override the global version with `pyenv local` or `pyenv shell`.