Python fails silently

Question

I am trying to get started with Python, so I installed Python 3.8, from python.org (on Windows 10). I remembered to check the "Add to PATH" during the installation and I have confirmed that it has been added to path, as seen in the first image.

However, when I try to use any commands, whether it be python --version or python HelloWorld.py, nothing happens. I have tried both the traditional command line as well as Powershell. I have also tried replacing python with python3, the result is the same. As you can see in the second image, I get no errors, just a blank line. So it's not that it cannot find Python at all, it rather seems that something is wrong with the installation.

Have anyone else encountered this kind of behavior? I have tried re-installing Python as well as removing old installations.

Image 1: Python seems to be correctly added to PATH.

Image 2: Python fails to return any output. But also no error. Same thing happens with python HelloWorld.py.

Update 1 - Here is what I have tried so far:

• Changing PATH to refer directly to exe file.
• Using both Command Prompt and PowerShell.
• Rebooting the PC.
• Re-installing Python (including removing old versions).
• Both the python and python3 command.

Update 2 - NameError: name 'python' is not defined

Update on the update: This was a wild goose chase. You are not supposed to be able to use that command in the interpreter, as described in this post.

So I tried to use the console from the python.exe file instead, and I got the following answer. However, from what I can find on it, it's normally a problem you encounter on elements of the code (like print()) and not on the python command...?

(image removed)

Update 3 - It works (kinda) If I use the command py --version or py test.py it works. I have no clue why though...

Answer 1

After extensive research, I still cannot find an answer to my own question. But I have found a work around, which minimizes the consequences:

Instead of using python, simply use py.

This will invoke the Python launcher instead of Python itself (from what I've read). For most people this will be good enough, but it is not the same. So it might cause issues and version mismatch in certain scenarios.

Also, despite of this weird behavior, Python seems to run fine in Visual Studio Code, when using the "Run" button (or the py command in the terminal).