win32 - ImportError: No module named bdiff

Jose M. Prieto jmprieto at
Mon Nov 13 06:18:27 CST 2006

Marcos Chaves wrote:
> I just started with Mercurial today. After installing the win32
> package (Mercurial-0.9.1-a27d90c9336e.exe) and cloning the main
> repository, if I try 'hg log', this is what i get:
> C:\dev\hg>hg log
> ** unknown exception encountered, details follow
> ** report bug details to
> ** or mercurial at
> ** Mercurial Distributed SCM (version unknown)
> Traceback (most recent call last):
> (snip)
> ImportError: No module named bdiff

This happens because you're running the hg from the cloned repo, not the one 
from the package you installed. If this is what you intended, you will need 
to build the modules (ensure you have the required tools and type "make 
local"). If this wasn't what you intended, you will need to type the full 
path to the correct hg executable, or remove hg.cmd from the cloned repo, or 
run the command from other directory. IIRC Windows always tries to run 
commands first from the working directory.

More information about the Mercurial mailing list