From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin now on Python 3? What about Mercurial?
Date: Fri, 02 Apr 2021 16:27:20 +0300 [thread overview]
Message-ID: <vriuy2e0yfyf.fsf@gavenkoa.example.com> (raw)
In-Reply-To: <f5229574-5704-fba1-16e5-22b4dc4a94d4@gmail.com>
On 2021-03-07, Marco Atzeri via Cygwin wrote:
> Mercurial has been just updated to version 5.7
> https://cygwin.com/packages/summary/mercurial.html
>
> and it now depends on python3.8
Just updated:
$ grep mercurial /var/log/setup.log.full
Installing file cygfile:///usr/lib/python3.8/site-packages/mercurial-5.7-py3.8.egg-info
and had a problem:
$ hg status
Traceback (most recent call last):
File "/usr/bin/hg", line 59, in <module>
dispatch.run()
File "/usr/lib/python3.8/site-packages/hgdemandimport/demandimportpy2.py", line 157, in __getattr__
self._load()
File "/usr/lib/python3.8/site-packages/hgdemandimport/demandimportpy2.py", line 97, in _load
_origimport, head, globals, locals, None, level
File "/usr/lib/python3.8/site-packages/hgdemandimport/demandimportpy2.py", line 44, in _hgextimport
return importfunc(name, globals, *args, **kwargs)
File "/usr/lib/python3.8/site-packages/mercurial/dispatch.py", line 21, in <module>
from .i18n import _
File "/usr/lib/python3.8/site-packages/hgdemandimport/demandimportpy2.py", line 257, in _demandimport
_origimport, name, globals, locals, level=level
File "/usr/lib/python3.8/site-packages/hgdemandimport/demandimportpy2.py", line 44, in _hgextimport
return importfunc(name, globals, *args, **kwargs)
File "/usr/lib/python3.8/site-packages/mercurial/i18n.py", line 15, in <module>
from .pycompat import getattr
File "/usr/lib/python3.8/site-packages/hgdemandimport/demandimportpy2.py", line 257, in _demandimport
_origimport, name, globals, locals, level=level
File "/usr/lib/python3.8/site-packages/hgdemandimport/demandimportpy2.py", line 44, in _hgextimport
return importfunc(name, globals, *args, **kwargs)
File "/usr/lib/python3.8/site-packages/mercurial/pycompat.py", line 38, in <module>
from .thirdparty.concurrent import futures
File "/usr/lib/python3.8/site-packages/hgdemandimport/demandimportpy2.py", line 257, in _demandimport
_origimport, name, globals, locals, level=level
File "/usr/lib/python3.8/site-packages/hgdemandimport/demandimportpy2.py", line 44, in _hgextimport
return importfunc(name, globals, *args, **kwargs)
ImportError: No module named concurrent
Fixed with:
bash# update-alternatives --config python
There are 3 programs which provide 'python'.
Selection Command
-----------------------------------------------
+ 1 /usr/bin/python2.7
2 /usr/bin/python3.6
* 3 /usr/bin/python3.8
Enter to keep the current selection[+], or type selection number: 3
That would be avoided (or problem delayed until impacted another utility) if
/usr/bin/hg had shebang /usr/bin/python3 instead of /usr/bin/python.
Thx for stabilizing Mercurial!
--
http://defun.work/
next prev parent reply other threads:[~2021-04-02 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 8:45 Russell VT
2021-03-04 11:05 ` marco atzeri
2021-03-04 15:19 ` Ken Brown
2021-03-04 18:32 ` Marco Atzeri
2021-03-06 14:45 ` Jari Aalto
2021-03-06 14:49 ` Marco Atzeri
2021-03-07 9:32 ` Russell VT
2021-03-07 11:58 ` Marco Atzeri
2021-04-02 13:27 ` Oleksandr Gavenko [this message]
2021-03-11 11:57 ` Jari Aalto
2021-03-04 13:30 ` Stephen John Smoogen
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=vriuy2e0yfyf.fsf@gavenkoa.example.com \
--to=gavenkoa@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).