Extending extension lookups

[Augie Fackler]

On Fri, Jan 15, 2016 at 10:01:06AM +0000, Martijn Pieters wrote:
> 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.

I'll take a look at your proposal some time today and get back to
you. I've got some rough concerns around package namespace management (yay).

>
> 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
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> https://selenic.com/mailman/listinfo/mercurial-devel