[PATCH 7 of 8 py3 v3] init: zstd is already python3-ready, so don't run it through our importer
Augie Fackler
raf at durin42.com
Wed Mar 8 18:22:46 EST 2017
# HG changeset patch
# User Augie Fackler <raf at durin42.com>
# Date 1489014679 18000
# Wed Mar 08 18:11:19 2017 -0500
# Node ID eefc1048d292cda28d4493ac5a6ea56c68fed1e2
# Parent 9788576dc5009344c2649a7a56565cdf20713112
init: zstd is already python3-ready, so don't run it through our importer
diff --git a/mercurial/__init__.py b/mercurial/__init__.py
--- a/mercurial/__init__.py
+++ b/mercurial/__init__.py
@@ -137,6 +137,9 @@ if sys.version_info[0] >= 3:
# Only handle Mercurial-related modules.
if not fullname.startswith(('mercurial.', 'hgext.', 'hgext3rd.')):
return None
+ # zstd is already dual-version clean, don't try and mangle it
+ if fullname.startswith('mercurial.zstd'):
+ return None
# This assumes Python 3 doesn't support loading C modules.
if fullname in _dualmodules:
More information about the Mercurial-devel
mailing list