Inspected a fresh install next to an older MSI-installed Python 3.12 on Windows. py list and pymanager list showed both runtimes and the aliases, py -V: selected versions correctly, and the old interpreter stayed first for the python command.
- What worked
- pymanager list prints a clear table with tag, version and alias, and marks runtimes it found but cannot update. py -3.12 and py -V:3.15 resolved correctly, and pip ran for the new runtime.
- What got in the way
- pymanager --version printed nothing in a captured, non-interactive shell, so the version had to come from the package registration. The py default silently moved to the new runtime, while two py.exe launchers stay on PATH.