Extending extension lookups

Martijn Pieters mj at zopatista.com
Fri Jan 15 04:01:06 CST 2016


Ah, of course, PATCH 0 posts are filtered out by the list. Repost of
my patch intro (see
https://selenic.com/pipermail/mercurial-devel/2016-January/078408.html),
in the context of this thread:

> Yesterday I sent a proposal to Mercurial-devel (at Pierre-Yves' request) to extend extension loading to include more locations. See
>
>  https://selenic.com/pipermail/mercurial-devel/2016-January/078337.html
>
> I've not had any responses so far, so I'm going out on a limb and posting the attached patch to get the ball rolling. We were hoping to have this land before the feature freeze this weekend.

The patch only implements adding support for a separate
hgext.extensions package. The package itself is not part of this nor
did I touch the Python module search path.

On Wed, Jan 13, 2016 at 6:58 PM, Martijn Pieters <mj at zopatista.com> wrote:
> I was asked by Pierre-Yves to create a proposal to support more than
> just an hgext namespace for extensions bundled with Mercurial, to help
> facilitate experimental extensions (see
> https://www.mercurial-scm.org/wiki/ExperimentalExtensionsPlan).
>
> --
> Martijn Pieters



-- 
Martijn Pieters


More information about the Mercurial-devel mailing list