Fwd: python 3.8.3 fails

[MRAB]

On 2020-06-13 15:41, Mats Wichmann wrote:
> On 6/11/20 8:58 AM, Avraham Markov wrote:
>> Please suggest something to fix
>> 
>> ---------- Forwarded message ---------
>> From: Avraham Markov <papaabramg at gmail.com>
>> Date: Thu, Jun 11, 2020 at 5:50 PM
>> Subject: python 3.8.3 fails
>> To: <python-list at python.org>
>> 
>> 
>> Hello, I successfully installed Python 3.8.3 (64-bit)
>> at Windows 10 LTSC 64 bit by python-3.8.3-amd64 installer
>> from https://www.python.org/downloads/windows/
>> Also by  python-3.8.3 installer,
>> but  lastly by  python-3.8.3-amd64 installer.
>> Then when I open powershell,
>> 
>> PS C:\Users\AlexJer> python
>> python : Python 3.8.3 (tags/v3.8.3:6f8c832, May 13 2020, 22:37:02) [MSC
>> v.1924 64 bit (AMD64)] on win32
>> At line:1 char:1
>> + python
>> + ~~~~~~
>>     + CategoryInfo          : NotSpecified: (Python 3.8.3 (t...MD64)] on
>> win32:String) [], RemoteException
>>     + FullyQualifiedErrorId : NativeCommandError
>> 
>> Type "help", "copyright", "credits" or "license" for more information.
>>>
> 
> For reasons which someone wiser in the ways of Powershell will have to
> describe, you have to run some programs programs with a more qualified
> name.  That is, try running:
> 
> python.exe
> 
> Alternatives:  the Python launcher doesn't have this limitation. Try
> running:
> 
> py
> 
> If you used the python.org installer, the Python Launcher is recommended
> anyway.
> 
> The Python install from the Microsoft Store also doesn't have that
> limitation, if you install that you should be able to run by typing just
> 
> python
> 
> There's probably some simple setup to make it work as we might
> expect/wish in Powershell... but the point is: there's nothing *wrong*
> with your setup.
> 
I have Windows 10 Home and the stock Python from python.org. Typing just 
"python" at the Powershell prompt starts Python without a problem.