Resolving relative imports does not consider the entire module path

[khatchad]

Currently, we only the module name and not the entire path when looking up local modules.

Suppose we have the following package structure:

E/
    __init__.py
    C/
        __init__.py
        A.py
    D/
        __init__.py
        B.py
D/
    __init__.py
    B.py
main.py

When we lookup the local module B.py, currently, we could get either one---E/D/B or D/B.

[khatchad]

Actually, this problem really only shows up in the relative import case, because, in other cases, the relative path (relative to PYTHONPATH) is included in the module name, e.g., E/C/A, when we get to com.ibm.wala.cast.python.parser.PythonModuleParser.getLocalModule(String).

[khatchad]

It would thus seem that, in the case that the import includes the module/package name, the resolved module name (i.e., with the periods removed) should also include the relative path (relative to PYTHONPATH).