From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: python3.9 failing?
Date: Tue, 21 Dec 2021 14:26:11 +0100 [thread overview]
Message-ID: <67c4a4f1-3189-e85a-0719-c05a1096a0d6@gmail.com> (raw)
In-Reply-To: <f5b1r26m7a2.fsf@ecclerig.inf.ed.ac.uk>
On 21.12.2021 14:12, Henry S. Thompson wrote:
> Sometime recently python3 stopped working, I suspect when it became
> patched through to python3.9.
>
> Cygcheck output attached.
>
> Here's some evidence from the command line...
> >: python3.9
> >: echo $?
> 127
Can you try
$ cygcheck /usr/bin/python3.9.exe
D:\cygwin64\bin\python3.9.exe
D:\cygwin64\bin\cygwin1.dll
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\KERNELBASE.dll
D:\cygwin64\bin\libpython3.9.dll
D:\cygwin64\bin\cygintl-8.dll
D:\cygwin64\bin\cygiconv-2.dll
Of course on my system the 3.9 is working fine as also alternatives
$ python3.9 --version
Python 3.9.9
Without Python 3.9 installed python3 should link by default to the next
in the line (likely 3.8)
$ alternatives --display python3
python3 - status is auto.
link currently points to /usr/bin/python3.9
/usr/bin/python3.6 - priority 36
/usr/bin/python3.7 - priority 37
/usr/bin/python3.8 - priority 38
/usr/bin/python3.9 - priority 39
Current `best' version is /usr/bin/python3.9.
Regards
Marco
next prev parent reply other threads:[~2021-12-21 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 13:12 Henry S. Thompson
2021-12-21 13:26 ` Marco Atzeri [this message]
2021-12-21 13:33 ` Achim Gratz
2021-12-23 5:50 ` Russell VT
2021-12-23 7:52 ` Marco Atzeri
2021-12-23 8:28 ` Russell VT
2021-12-23 8:50 ` Marco Atzeri
2021-12-23 20:00 ` Henry S. Thompson
2021-12-21 13:36 ` Marco Atzeri
2021-12-21 18:10 ` Henry S. Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67c4a4f1-3189-e85a-0719-c05a1096a0d6@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).