No completion in namespace packages

[MikhailArkhipov]

.
├── projecta
│   └── foo
│       ├── bar
│       │   └── __init__.py
│       └── __init__.py
└── projectb
    └── foo
        ├── baz
        │   └── __init__.py
        └── __init__.py

test.py:

import projectA.foo
import projectA.foo.bar
import projectB.foo
import projectB.foo.baz

projectA.

Jedi:

PyCharm:

[MikhailArkhipov]

Works in 3.6 but not in 2.7. 2.7 works if __init__.py is added to ProjectA and ProjectB. See also https://stackoverflow.com/questions/32152373/python-why-can-i-import-modules-without-init-py-at-all

[MikhailArkhipov]

Apparently is is pretty common case. See
microsoft/vscode-python#2213 and
microsoft/vscode-python#2319

mpl_toolkits does not have __init__.py, just bunch of subfolders. Adding __init__.py makes us import the module.

[zooba]

2.7 doesn't support namespace packages - they were added in 3.3.

mpl_toolkits should be coming through AstPythonInterpreter.ImportModule, so it should be easy enough to look through all search paths and return a set of multiple modules.

The original issue in this thread is about namespace packages in the user's own project, which is going to be a different fix. You'll probably want to split the "in stdlib" vs "in project" cases into separate bugs.

[MikhailArkhipov]

Yes, I know. Matplotlib issue is somewhat simpler.

[MikhailArkhipov]

microsoft/python-language-server#12