#1147 Pydev fails importing projects with nested wildcard imports.

[Nathan Rice]

When I import the top level namespace of a third party project (in this case networkx) and use methods available in that namespace that have been made available by nested wildcard imports, PyDev reports that the module does not contain the method, although Python has no problems with it.

For example, if I do the following:

import networkx as nx
g = nx.DiGraph()

PyDev will bark at me. This happens with the majority of classes/methods in this package, because of the way they are set up. The networkx package has sub-packages like classes, algorithms, etc. In each of those sub-packages there are additional modules. The __init__.py for each package imports all sub-modules/sub-packages under it into its namespace. This continues all the way up to the top level (networkx) package, so its namespace includes everything from all sub-modules and sub-packages in the project. This also has happened to me with some other projects but it is fairly uncommon. While I don't think this is the best way to use a project's namespace I do think PyDev should support it if the python interpreter supports it.