thirdparty: don't make zope a namespace package
authorGregory Szorc <gregory.szorc@gmail.com>
Wed, 21 Mar 2018 19:49:07 -0700
changeset 37177 338367d44d34
parent 37176 943d77fc07a3
child 37178 68ee61822182
thirdparty: don't make zope a namespace package There are a gazillion zope.* packages in the wild. So zope/__init__.py needs to be a namespace package. But in Mercurial, we have 1 zope package. And even if we had multiple packages, they'd all be in thirdparty/zope/. So we don't need a namespace package. Differential Revision: https://phab.mercurial-scm.org/D2929
mercurial/thirdparty/zope/__init__.py
--- a/mercurial/thirdparty/zope/__init__.py	Wed Mar 21 19:48:50 2018 -0700
+++ b/mercurial/thirdparty/zope/__init__.py	Wed Mar 21 19:49:07 2018 -0700
@@ -1,7 +0,0 @@
-# this is a namespace package
-try:
-    import pkg_resources
-    pkg_resources.declare_namespace(__name__)
-except ImportError:
-    import pkgutil
-    __path__ = pkgutil.extend_path(__path__, __name__)