Extending extension lookups

Augie Fackler raf at durin42.com
Tue Jan 19 10:32:03 CST 2016


On Tue, Jan 19, 2016 at 10:49 AM, Martijn Pieters <mj at zopatista.com> wrote:
> The underlying goal was to separate release cycles and contribution
> requirements for the experimental extensions from the main mercurial
> repo. See https://www.mercurial-scm.org/wiki/ExperimentalExtensionsPlan.
>
> I'm not specifically attached to hgext/experimental in that respect;
> if a separate package (`hgext_experimental`, for example) works better
> to facilitate the goal of separation then so be it.


It probably does, if only because namespace packages are such a woeful
disaster in Python. If we don't nest this inside an existing hg-owned
namespace, then it's easy for people to (say) pick up their system hg
(living in dist-packages), but still use our experiments from pip (in
site-packages). Does that make sense?


More information about the Mercurial-devel mailing list