[PATCH 3 of 3] extensions: also search for extension in the 'hgext3rd' package

[timeless]

It isn't useful.

If we want to have a --debug which lists the search path, that's fine.

But for normal "did load" cases, we shouldn't show failures to find
extensions in earlier parts of the path.

When I run `echo hi` with a PATH of:
/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin

I don't get:
 -bash: /usr/local/bin/echo: command not found
hi

I just get:
hi

On Mon, Mar 14, 2016 at 9:00 AM, Pierre-Yves David
<pierre-yves.david at ens-lyon.org> wrote:
>
>
> 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.
>
> --
> Pierre-Yves David