diff options
author | Aurelien Campeas <aurelien.campeas@logilab.fr> | 2012-07-30 11:22:03 +0200 |
---|---|---|
committer | Aurelien Campeas <aurelien.campeas@logilab.fr> | 2012-07-30 11:22:03 +0200 |
commit | 62126b894bc1d1c6a88db5bf4cae86ea20b48d6e (patch) | |
tree | 91711fee01fc8f182c89b5001996d7a9010d76ee /modutils.py | |
parent | 507c60ba25e29654ec1a6245d684fb0d96dd12b5 (diff) | |
download | logilab-common-62126b894bc1d1c6a88db5bf4cae86ea20b48d6e.tar.gz |
[modutils] fix load_module_from_path (closes #100935)
A very old bug in modutils, that leads to doubly loading some modules.
By chance on Linux (or the platform we typically use) it seems one the two module
gets forgoten as soon as loaded.
Unfortunately on Windows, with CubicWeb, it was found that the first module instance
was the one on which the mro was built and the second one hosted the super(...)
call with a different class id for the litteral within super(ThisClass, self)....
The exact reason for the dual behaviour is still unknown but it could well be
one of those 'platform dependant' bits that riddle Python.
Diffstat (limited to 'modutils.py')
-rw-r--r-- | modutils.py | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/modutils.py b/modutils.py index 2aa4ce3..ebad473 100644 --- a/modutils.py +++ b/modutils.py @@ -158,6 +158,9 @@ def load_module_from_modpath(parts, path=None, use_sys=1): if len(modpath) != len(parts): # even with use_sys=False, should try to get outer packages from sys.modules module = sys.modules.get(curname) + elif use_sys: + # because it may have been indirectly loaded through a parent + module = sys.modules.get(curname) if module is None: mp_file, mp_filename, mp_desc = find_module(part, path) module = load_module(curname, mp_file, mp_filename, mp_desc) |