1. Sebastian Sebastian
  2. scm-manager
  3. Issues

Issues

Issue #93 duplicate

No module named mercurial

Lorenzo Petrone
created an issue

I have the same problem described in #64, I'm not sure if it actually //is// the same bug or not. Here's the log:

{{{

!18:00:15.287 [qtp374961130-22] WARN sonia.scm.web.cgi.DefaultCGIExecutor - process ends with exit code 1

18:00:15.405 [Thread-31] WARN sonia.scm.web.cgi.DefaultCGIExecutor - Traceback (most recent call last): File "/Users/looris/.scm/cgi-bin/hgweb.py", line 44, in <module> from mercurial import demandimport; demandimport.enable() ImportError: No module named mercurial

18:00:15.407 [qtp374961130-25] WARN sonia.scm.web.cgi.DefaultCGIExecutor - process ends with exit code 1 18:00:15.522 [Thread-32] WARN sonia.scm.web.cgi.DefaultCGIExecutor - Traceback (most recent call last): File "/Users/looris/.scm/cgi-bin/hgweb.py", line 44, in <module> from mercurial import demandimport; demandimport.enable() ImportError: No module named mercurial

18:00:15.524 [qtp374961130-26] WARN sonia.scm.web.cgi.DefaultCGIExecutor - process ends with exit code 1

}}}

Comments (5)

  1. Sebastian Sebastian repo owner
    • changed status to new

    It seems you are using a python version, which does not know the mercurial modules.

    You have two options:

    • Configure a python version, which knows the mercurial modules
    • Configure a python module path

    Both options are configurable under Config->Repository Types->Mercurial

  2. stoneMcClane

    I've got the same problem with the 1.20 version and the latest snapshot. I tried using a pre-existing python installation on my computer as well as the preconfigured package that is installed via the SCM web-interface. It always gave me the above error when I tried to clone/pull/push a mercurial repository.

    Finally, adding the SCM hg module path to the $PYTHONPATH environment variable helped, i.e. I placed the following at the top of scm-server.bat

    set PYTHONPATH=%PYTHONPATH%;C:\Users\myuser\.scm\pkg\f1ea71\hg\2.1\lib
    

    The very same path was automatically configured in the SCM web-interface when I installed the package, but it seems that this had no effect.

  3. Log in to comment