Mercurial > hg
comparison mercurial/__init__.py @ 32521:942051a29fb6
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.
author | Augie Fackler <raf@durin42.com> |
---|---|
date | Sun, 28 May 2017 15:45:47 -0400 |
parents | 397e3a2e9347 |
children | 5d0c0c8d2929 |
comparison
equal
deleted
inserted
replaced
32520:dc0da9829c29 | 32521:942051a29fb6 |
---|---|
31 # Only handle Mercurial-related modules. | 31 # Only handle Mercurial-related modules. |
32 if not fullname.startswith(('mercurial.', 'hgext.', 'hgext3rd.')): | 32 if not fullname.startswith(('mercurial.', 'hgext.', 'hgext3rd.')): |
33 return None | 33 return None |
34 # zstd is already dual-version clean, don't try and mangle it | 34 # zstd is already dual-version clean, don't try and mangle it |
35 if fullname.startswith('mercurial.zstd'): | 35 if fullname.startswith('mercurial.zstd'): |
36 return None | |
37 # pywatchman is already dual-version clean, don't try and mangle it | |
38 if fullname.startswith('hgext.fsmonitor.pywatchman'): | |
36 return None | 39 return None |
37 | 40 |
38 # Try to find the module using other registered finders. | 41 # Try to find the module using other registered finders. |
39 spec = None | 42 spec = None |
40 for finder in sys.meta_path: | 43 for finder in sys.meta_path: |