Python commands don't work with Python Install Manager

[splatteredbits]

Describe the bug

After installing Python Install Manager and after Python Install Manager installs a default runtime, 3.13.5, python commands still don't work:

> python -c "import sys; print(sys.executable);"
Usage:
    py <regular Python options>
                         Launch the default runtime with specified options. This
                         is the equivalent of the python command.
    py -V:<TAG>          Launch runtime identified by <TAG>, which should
                         include the company name if not PythonCore. Regular
                         Python options may follow this option.
    py -3<VERSION>       Equivalent to -V:PythonCore\3<VERSION>. The version
                         must begin with the digit 3, platform overrides are
                         permitted, and regular Python options may follow. py -3
                         is the equivalent of the python3 command.
    py exec <any of the above>
                         Equivalent to any of the above launch options, and the
                         requested runtime will be installed if needed.
    py help [<CMD>]      Show help for Python installation manager commands
    py install <TAG>     Download new Python runtimes, or pass --update to
                         update existing installs.
    py list [<FILTER>]   Show installed Python runtimes, optionally filtering by
                         <FILTER>.
    py uninstall <TAG>   Remove one or more runtimes from your machine. Pass
                         --purge to clean up all runtimes and cached files.

Find additional information at https://docs.python.org/dev/using/windows.

To Reproduce
Steps to reproduce the behavior:

1. Install Python Install Manager.
2. Install Python 3.13.5: pymanager install 3.13.5.
3. Run python -c "import sys; print(sys.executable)".
4. Note the error.

Expected behavior

I expect that python commands work after Python Install Manager installs at least one runtime.

Additional context

I'm trying to get Python installed and configured on unattended, non-interactive Jenkins build agent servers. These build servers run Node.js builds, which includes installing Node.js modules. Some modules execute python commands when they get installed. These python commands are currently failing because of this problem.

[zooba]

That's very strange - you don't have an alias that replaces python with py do you? There's no code path in python.exe that should ever end up showing help.

What install commands did you use?

[Cologler]

I installed PyManager via winget today (winget install Python.PythonInstallManager), and I tried to run it with PowerShell.

The & "C:\Program Files\PyManager\python3.exe" and & "C:\Program Files\PyManager\py.exe" work, but & "C:\Program Files\PyManager\python.exe" did not work.

& "C:\Program Files\PyManager\py.exe" --version
---> Python 3.13.5

& "C:\Program Files\PyManager\python3.exe" --version
---> Python 3.13.5

& "C:\Program Files\PyManager\python.exe" --version
---> Usage:
    py <regular Python options>
                         Launch the default runtime with specified options. This
                         is the equivalent of the python command.
    py -V:<TAG>          Launch runtime identified by <TAG>, which should
                         include the company name if not PythonCore. Regular
                         Python options may follow this option.
    py -3<VERSION>       Equivalent to -V:PythonCore\3<VERSION>. The version
                         must begin with the digit 3, platform overrides are
                         permitted, and regular Python options may follow. py -3
                         is the equivalent of the python3 command.
    py exec <any of the above>
                         Equivalent to any of the above launch options, and the
                         requested runtime will be installed if needed.
    py help [<CMD>]      Show help for Python installation manager commands
    py install <TAG>     Download new Python runtimes, or pass --update to
                         update existing installs.
    py list [<FILTER>]   Show installed Python runtimes, optionally filtering by
                         <FILTER>.
    py uninstall <TAG>   Remove one or more runtimes from your machine. Pass
                         --purge to clean up all runtimes and cached files.

Find additional information at https://docs.python.org/dev/using/windows.

View online help? [y/N] n

[Cologler]

It might be a winget issue.

By default, running

winget install Python.PythonInstallManager

installs it with machine scope.

I uninstalled it and reinstalled using:

winget install Python.PythonInstallManager --scope user

Now, the output is correct:

& "C:\Program Files\WindowsApps\PythonSoftwareFoundation.PythonManager_25.0.187.0_x64__3847v3x7pw1km\python.exe" --version

---> Python 3.13.5

---

I suspect this python.exe is intended for internal use by PythonManager. However, when installed with machine scope, it adds itself to the system PATH, which ends up overriding my other Python installations.

However, I still don’t understand why

& "C:\Program Files\PyManager\python.exe" --version

produces such a strange output.

[zooba]

We aren't involved in the WinGet manifest, so if it's not working, you'll have to report it on their repository first.

If you do that and they are convinced it's due to upstream, then link their issue here and we can take a look. Otherwise, we list some supported/advanced ways to install the Python Install Manager in our docs.