failed to import extension evolve: No module named evolve
Faheem Mitha
faheem at faheem.info
Tue Mar 13 04:55:41 UTC 2018
On Mon, 12 Mar 2018, Malachi de Ælfweald wrote:
> Per the instructions, I installed the extension via pip:
[snip]
> And added the extension to my ~/.hgrc:
> [extensions]
> mq =
> color =
> hgk =
> convert =
> purge =
> evolve =
> Whenever I try to run any hg command, it complains that it can't import the evolve extension:
> $ hg status
> *** failed to import extension evolve: No module named evolve
> It doesn't complain about any other extension. They've been working.
[snip]
> but, of course, we can't point to that file in the .hgrc
Yes, you can. See, for example
https://www.mercurial-scm.org/wiki/UsingExtensions
######################################################################
2. Enabling an extension
To enable the "foo" extension, either shipped with Mercurial or in the
Python search path, create an entry for it in your hgrc, like this:
[extensions]
foo =
You may also specify the full path to an extension (which may be either a
.py file or a folder containing __init__.py):
[extensions]
myfeature = ~/.hgext/myfeature.py
######################################################################
> $ hg -v --version
> *** failed to import extension evolve: No module named evolve
> Mercurial Distributed SCM (version 3.7.3)
>
> $ uname -a
> Linux enki 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> $ python --version
> Python 2.7.12
>
>
>
> Thoughts?
>
> Malachi de Ælfweald
> http://www.google.com/profiles/malachid
>
>
More information about the Evolve-testers
mailing list