Hey, @kirankotari

feel free to drop some comments so I can make a fix. I really want this feature :)

At this point I see the only problem in -arm support, because I don't know how to handle & test this properly; I can see that some functions can't handle the arm versions too, e.g. there is still function Is32Bit which is used for -win32 postfix auto-resolution in pyenv-install, and so on...

btw, my changes did nothing to the old-styled commands, it is still possible to use install/global/local by providing full version name, so no conflicts and all tests pass fine

Sooo

I noticed the #505 issue and decided to work on it, because I think it is the part of pyenv-latest feature. I checked the original pyenv behavior and from now auto-resolution feature finally should work the same way.

It's still possible to use the exact version...

PS C:\Users\uhx\Projects\pyenv-win> .\pyenv-win\bin\pyenv.bat local 3.11.2-win32
PS C:\Users\uhx\Projects\pyenv-win> type .\.python-version
3.11.2-win32
PS C:\Users\uhx\Projects\pyenv-win> .\pyenv-win\bin\pyenv.bat exec python -c "import sys; print(sys.version)"
3.11.2 (tags/v3.11.2:878ead1, Feb  7 2023, 16:24:28) [MSC v.1934 32 bit (Intel)]

But from now you can pin just a minor (or major) version and run install / exec

PS C:\Users\uhx\Projects\pyenv-win> .\pyenv-win\bin\pyenv.bat local
3.7
PS C:\Users\uhx\Projects\pyenv-win> .\pyenv-win\bin\pyenv.bat install
:: [Info] ::  Mirror: https://www.python.org/ftp/python
:: [Installing] ::  3.7.9 ...
:: [Info] :: completed! 3.7.9
PS C:\Users\uhx\Projects\pyenv-win> .\pyenv-win\bin\pyenv.bat exec python --version
Python 3.7.9

So the local/global command should just pin unchanged user input, as pyenv does:

root@f2a41ae37ecf:~# /root/.pyenv/bin/pyenv local 3.11 3.10
root@f2a41ae37ecf:~# /root/.pyenv/bin/pyenv exec python --version
Python 3.11.2
root@f2a41ae37ecf:~# /root/.pyenv/bin/pyenv local
3.11
3.10

The previous behavior of these commands was to modify the user input (resolve version/add postfix) and then save it to the ".python-version". From now we pin the original user input (if it's correct) and resolve it each time we call python shims. Check the updated tests if you can't catch this.