setop/pyenv
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

README: clarify behavior of pyenv latest

Browse Source
This commit is contained in:
Michael Rienstra 2023-02-27 16:26:18 -08:00 committed by GitHub
parent 3bfc97ad29
commit ecab7b0d17
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -416,7 +416,7 @@ please visit the wiki page about
All Pyenv subcommands except `uninstall` automatically resolve full prefixes to the latest version in the corresponding version line. All Pyenv subcommands except `uninstall` automatically resolve full prefixes to the latest version in the corresponding version line.
`pyenv install` picks the latest known version while other subcommands -- the latest installed version. `pyenv install` picks the latest known version, while other subcommands pick the latest installed version.
E.g. to install and then switch to the latest 3.10 release: E.g. to install and then switch to the latest 3.10 release:
@ -425,8 +425,7 @@ pyenv install 3.10
pyenv global 3.10 pyenv global 3.10
``` ```
You can run [`pyenv latest <prefix>`](COMMANDS.md#pyenv-latest) to see You can run [`pyenv latest -k <prefix>`](COMMANDS.md#pyenv-latest) to see how `pyenv install` would resolve a specific prefix, or [`pyenv latest <prefix>`](COMMANDS.md#pyenv-latest) to see how other subcommands would resolve it.
what a specific prefix would be resolved to.
See the [`pyenv latest` documentation](COMMANDS.md#pyenv-latest) for details. See the [`pyenv latest` documentation](COMMANDS.md#pyenv-latest) for details.