pyenv
Can anybody explain how/why this might happen?
","upvoteCount":1,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Pyenv creates shims for all executables that exist in Pyenv-managed installations.
\nIndeed, if you don't have any Pyenv-managed installations -- e.g. right after installaing Pyenv, or if you uninstall them all -- there would be no shims at all.
That's because Pyenv needs a facility to redirect them if any of the ways to select an alternative version is activated (the PYENV_VERSION envvar and .python-version files).
Why does pyenv shim a version of python it didn't install? #2840
-
Can anybody explain how/why this might happen? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Pyenv creates shims for all executables that exist in Pyenv-managed installations. That's because Pyenv needs a facility to redirect them if any of the ways to select an alternative version is activated (the |
Beta Was this translation helpful? Give feedback.
Pyenv creates shims for all executables that exist in Pyenv-managed installations.
Indeed, if you don't have any Pyenv-managed installations -- e.g. right after installaing Pyenv, or if you uninstall them all -- there would be no shims at all.
That's because Pyenv needs a facility to redirect them if any of the ways to select an alternative version is activated (the
PYENV_VERSIONenvvar and.python-versionfiles).