Fwd: python 3.8.3 fails

Avraham Markov

unread,

Jun 11, 2020, 1:02:16 PM6/11/20

to

Please suggest something to fix

---------- Forwarded message ---------
From: Avraham Markov <papaa...@gmail.com>
Date: Thu, Jun 11, 2020 at 5:50 PM
Subject: python 3.8.3 fails
To: <pytho...@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.
>
>>

Thanks,
Avraham

MRAB

unread,

Jun 11, 2020, 2:59:22 PM6/11/20

to

After typing "python", you have "python : " at the start of the next
line. That's what it doesn't like. Where does that come from?

Mats Wichmann

unread,

Jun 13, 2020, 10:41:40 AM6/13/20

to

On 6/11/20 8:58 AM, Avraham Markov wrote:
> Please suggest something to fix
>
> ---------- Forwarded message ---------
> From: Avraham Markov <papaa...@gmail.com>
> Date: Thu, Jun 11, 2020 at 5:50 PM
> Subject: python 3.8.3 fails
> To: <pytho...@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.

MRAB

unread,

Jun 13, 2020, 12:11:06 PM6/13/20

to

I have Windows 10 Home and the stock Python from python.org. Typing just
"python" at the Powershell prompt starts Python without a problem.

moi

unread,

Jun 14, 2020, 6:10:26 AM6/14/20

to

win 1252 platforms

Python (eg 3.8.3) is not working properly in PowerShell/pwsh (6 or 7).
Always the same story.

Python 3.2 works perfectly. However, one should configure PowerShell
to use Windows-1252.

moi

unread,

Jun 14, 2020, 11:38:36 AM6/14/20

to

Le samedi 13 juin 2020 18:11:06 UTC+2, MRAB a écrit :

PS D:\jm> shenc
[Console]::OutputEncoding ->
CodePage : 1252
[Console]::InputEncoding ->
CodePage : 1252
$OutputEncoding ->
CodePage : 1252
PS D:\jm> py38
Python 3.8.3 (tags/v3.8.3:6f8c832, May 13 2020, 22:20:19) [MSC v.1925 32 bit (Intel)] on win32

Type "help", "copyright", "credits" or "license" for more information.

>>> ^Z

PS D:\jm> jcp(20297)
PS D:\jm> shenc
[Console]::OutputEncoding ->
CodePage : 20297
[Console]::InputEncoding ->
CodePage : 20297
$OutputEncoding ->
CodePage : 20297
PS D:\jm> py38

D:\jm>ÁÄÇ?€?ÃÃŽêá(€ ÁÄÇ?€?ÃÃ€Á 1>ÁŽŽêá(€ÄÇÄø€‘ • ŽŽêá(€Äš* & µÈÇ?1>†ÁÌÁ€
La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.
La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.

D:\jm>‘€
'‘€' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

D:\jm> €
' €' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

D:\jm>“€
'“€' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

D:\jm>”€
'”€' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

D:\jm>•€
'•€' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

D:\jm>–€
'–€' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

D:\jm>œ€
'œ€' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

D:\jm>˜€
'˜€' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

D:\jm>™ŽÄš* & µÈÇ?1>†ÁÌÁ€
'™ŽÄš*' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
La syntaxe du nom de fichier, de répertoire ou de volume est incorrecte.

D:\jm>ŠŽ
'ŠŽ' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
PS D:\jm>
PS D:\jm>

--------

A tiny C# app, (?? are correct)

PS D:\jm> c:\zzz\textcs.exe
abcé??

A go app

PS D:\jm> c:\zzz\textgoö.exe
abcéœ€
PS D:\jm>

moi

unread,

Jun 14, 2020, 11:55:33 AM6/14/20

to

Addendum

I presented a bootstrap issue.

When Python starts, it is really not working properly
(due to its "internal coding of characters").

Terry Reedy

unread,

Jun 14, 2020, 4:02:41 PM6/14/20

to

On 6/13/2020 2:38 PM, Dennis Lee Bieber wrote:
> On Sat, 13 Jun 2020 17:10:46 +0100, MRAB <pyt...@mrabarnett.plus.com>
> declaimed the following:

>
>> I have Windows 10 Home and the stock Python from python.org. Typing just
>> "python" at the Powershell prompt starts Python without a problem.
>

> 99 44/100% sure what the OP called "PowerShell" is "PowerShell ISE",
> not a PowerShell console. In my testing ISE intercepts STDIN and STDERR --
> Interactive Python dumps its banner message on STDERR. ISE intercepts that
> banner and tries to interpret it as a PowerShell error object, which fails,
> causing a PowerShell error dump to be shown. The interception of STDIN
> prevents the Python >>> prompt from receiving any input. Buffering of
> STDOUT is also in play...
>
> -=-=-=- ISE (using <ctrl-c> to abort hanging commands)
> PS C:\Users\Wulfraed> python -c "print(input('type something'))"
>
> PS C:\Users\Wulfraed> python -c "x = input('Enter something '); print(x)"
>
> PS C:\Users\Wulfraed> python -c "x = input('Enter something\n '); print(x)"
> Enter something
>
> PS C:\Users\Wulfraed>
>
>
> -=-=-=- PS console window
> PS C:\Users\Wulfraed> python -c "print(input('type something'))"
> type somethingabc
> abc
> PS C:\Users\Wulfraed> python -c "x = input('Enter something '); print(x)"
> Enter something abcd
> abcd
> PS C:\Users\Wulfraed> python -c "x = input('Enter something\n '); print(x)"
> Enter something
> something
> something
> PS C:\Users\Wulfraed>

Could you open a tracker issue to put 'Do not use PowerShell IDE' is the
Windows chapter of 'Using Python'? This is obviously not common
knowledge? Or open as a possible bug issue. Maybe the install can be
done a big differently.

--
Terry Jan Reedy