Intellisense is broken in the presence of relative imports

[zjturner]

If you type this:

from . import foo

PTVS doesn't seem to understand this syntax. After you write the . (note the space) you get an intellisense popup suggesting module names, so as you continue typing import it selects importlib and you end up with

from . importlib foo

The modules that its suggesting in this intellisense popup are not located in the specified directory either it just seems to be all the modules in the search paths. So I think PTVS simply has no concept of relative imports.

If you actually go and type out a valid relative import, it is able to resolve it. So something like

from ..foo import bar

if it is a valid module, you will have working intellisense on bar and no squigglies. The problem seems to be isolated only to the case of typing the import statement.

[zooba]

The tricky thing here is that from . module import ... is totally valid, so we really need to interleave the import keyword here. (Turns out that import is not a usable module name, which is handy.)

[zjturner]

Ugh, I looked at the grammar of the import statement, you're right.

Yea in that case I guess you'd want to interleave the import keyword, but only if a space precedes (because you can't write from .import foo, it has to be from . import foo)

But really just having some level of relative import support would be nice, even if there are some edge cases. For example, if I type from . it would be nice if the IntelliSense popup was filtered to only those modules that are in ., and if I typed from .. it would dynamically update the list to only those modules that are visible in .., etc.

Of course, proper handling of the import keyword would make it even better.

[zjturner]

Has this bug been fixed?

[zooba]

You're right, it hasn't. We were a bit hasty closing this one and misread it (we did a really quick run over all our old issues today to try and clean up a bit).

We get completions for members of relative imports, but once imported we lose any idea of what they are. We also don't properly handle the . import or .<module> cases.

[Jman420]

Any chance of an update on this issue? This causes huge slow-downs for me during development time, needing to open modules I've referenced through relative imports in a text editor and make sure I am calling correct methods, attributes, etc.