[Bug 5340] New: Don't install meta-path importer during package build

bugzilla at mercurial-scm.org bugzilla at mercurial-scm.org
Wed Aug 24 13:38:37 UTC 2016


https://bz.mercurial-scm.org/show_bug.cgi?id=5340

            Bug ID: 5340
           Summary: Don't install meta-path importer during package build
           Product: Mercurial
           Version: default branch
          Hardware: PC
                OS: Mac OS
            Status: UNCONFIRMED
          Severity: bug
          Priority: wish
         Component: Mercurial
          Assignee: bugzilla at selenic.com
          Reporter: jaraco at jaraco.com
                CC: mercurial-devel at selenic.com

In [Velociraptor
#203](https://bitbucket.org/yougov/velociraptor/issues/203/tests-failing-when-creating-egg_info),
we discovered an issue in how Mercurial resolves its version for package
metadata that causes problems during building under Setuptools (which builds
its packages in-process).

Although it's conceivable that Setuptools could be rewritten to use a different
sandboxing technique that performs better isolation, or that it could
explicitly manage the sandboxing of metapath importers, I think it's also
reasonable that no setup script should be installing metapath importers.

Would Mercurial consider another technique in the setup script that doesn't
involve invoking the metapath importer installation?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list