[PATCH 3 of 3] extensions: also search for extension in the 'hgext3rd' package
pierre-yves.david at ens-lyon.org
Mon Mar 14 09:00:51 EDT 2016
On 03/13/2016 02:04 AM, timeless wrote:
> I'm not a fan of getting the import error repeatedly. I don't mind
> getting multiple parse errors if a module exists (broken) in multiple
> places. But seeing something say "couldn't find x in a; couldn't find x
> in b; couldn't find x in c" seems silly. Also, I don't see the point of
> "couldn't find x in a; found it in b".
I'm not sure what is the issue here, it is debug message that provide a
clear depiction of the extensions search. I expect it to be useful.
More information about the Mercurial-devel