Latest update seems to have broken Mercurial
David Monksfield
dmdm@dmbrain.co.uk
Sun Jan 31 10:25:44 GMT 2021
On Sat, 30 Jan 2021 14:09:20 +0100, Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
> On 30.01.2021 10:41, David Monksfield wrote:
> > Mercurial was working fine for me until my last Cywin update (yesterday).
> > [...]
>
> Hi David,
> yes I am aware, current mercurial package still requires python 2.7.
>
> You can see the situation with
>
> -------------------------------------------
> $ alternatives --display python
> python - status is auto.
> link currently points to /usr/bin/python3.8
> /usr/bin/python3.7 - priority 37
> /usr/bin/python2.7 - priority 27
> /usr/bin/python3.6 - priority 36
> /usr/bin/python3.8 - priority 38
> Current `best' version is /usr/bin/python3.8.
> -----------------------------------------
>
> and change it with
>
> -----------------------------------------
> $ alternatives --config python
Brilliant, thanks - that worked!
I'll make sure I change the python default back to 3.8 once the Mercurial package has been updated.
David
More information about the Cygwin
mailing list