[PATCH 1 of 2] When failing to load an extension, show where Hg tried to load it from

Jesse Glick jesse.glick at sun.com
Mon Mar 3 11:47:15 CST 2008

Thomas Arendsen Hein wrote:
> This doesn't look good for extensions defined with
> [extensions]
> foo =
> (i.e. without a path specified so the sys.path is used)
> Example:
> *** failed to import extension foo from : invalid syntax (foo.py, line 40)

Good point, will resubmit with fix.

More information about the Mercurial-devel mailing list