loader: pywatchman appears to already be py3 compatible
authorAugie Fackler <raf@durin42.com>
Sun, 28 May 2017 15:45:47 -0400
changeset 32521 942051a29fb6
parent 32520 dc0da9829c29
child 32522 9ed70525fd6e
loader: pywatchman appears to already be py3 compatible Our loader was doing some confusing things in pywatchman, but it looks like we shouldn't be using it there anyway.
mercurial/__init__.py
--- a/mercurial/__init__.py	Sun May 28 17:02:24 2017 -0400
+++ b/mercurial/__init__.py	Sun May 28 15:45:47 2017 -0400
@@ -34,6 +34,9 @@
             # zstd is already dual-version clean, don't try and mangle it
             if fullname.startswith('mercurial.zstd'):
                 return None
+            # pywatchman is already dual-version clean, don't try and mangle it
+            if fullname.startswith('hgext.fsmonitor.pywatchman'):
+                return None
 
             # Try to find the module using other registered finders.
             spec = None