public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: python3.9 failing?
Date: Thu, 23 Dec 2021 08:52:07 +0100	[thread overview]
Message-ID: <2839cd60-8219-4b9a-b967-9519a36d247e@gmail.com> (raw)
In-Reply-To: <CANV2+nWPJE83rryNzJwwVNsKYbzvJnKV9GZ93ERzD95Zpb7QJg@mail.gmail.com>

On 23.12.2021 06:50, Russell VT wrote:
> On Tue, Dec 21, 2021 at 6:34 AM Achim Gratz <Stromeko@nexgo.de> wrote:
> 
>> Marco Atzeri writes:
>>> Without Python 3.9  installed python3 should link by default to the
>>> next in the line (likely 3.8)
>>
>> While python3 still defaults to python38 alternatives should probably
>> prioritize 38 over 39?
> 
> 
> That's how I "fixed" mercurial on my own installation, as it was
> complaining about missing the "parsers" module, from inside the Python 3.9
> libraries, IIRC.
> 

Thanks for the report.
It is caused by:


$ head /usr/bin/hg -n 20
#!/usr/bin/python3
                  ^^ default 3.9
....

libdir = '../lib/python3.8/site-packages'
                        ^^ but really need 3.8
...


No surprise is not working.

A simple workaround is:


$ cp /usr/bin/hg /usr/local/bin/

$ sed -i -e "1 s/python3$/python3.8/" /usr/local/bin/hg

$ hg --version
Mercurial Distributed SCM (version 6.0)
(see https://mercurial-scm.org for more information)

...

Regards
Marco



  reply	other threads:[~2021-12-23  7:52 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
2021-12-21 13:33   ` Achim Gratz
2021-12-23  5:50     ` Russell VT
2021-12-23  7:52       ` Marco Atzeri [this message]
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=2839cd60-8219-4b9a-b967-9519a36d247e@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).