[Language Server] "Unable to resolve module" for app project

Environment data

• VS Code version: Version 1.25.1 (1.25.1)
• Extension version (available under the Extensions sidebar): 2018.7.0
• OS and version: macOS 10.13.6
• Python version (& distribution if applicable, e.g. Anaconda): 3.6.3
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): virtualenv
• Relevant/affected Python packages and their versions: XXX

Actual behavior

I have a few directories that form my python workspace. Each directory is a separate python project (either app, that’s executed, or library, that has setup.py and is installed) with a separate env configured inside vscode. I’ve turned on new “language server” feature.

Imports from my app are underlined and say “Unable to resolve <module>. Intellisense may be missing.” Imports from my libs work fine.

Expected behavior

I’d like language server to process apps as well (autocomplete, goto, etc.)

Logs

Starting Microsoft Python language server.
[Info  - 10:43:22 PM] Created Microsoft.PythonTools.Interpreter.Ast.AstPythonInterpreter instance from Microsoft.PythonTools.Interpreter.Ast.AstPythonInterpreterFactory
Initializing for /Users/yevhen/.virtualenvs/<app_project>/bin/python

[eikonomega]

I’m also having the same issue.

VS Code version: Version 1.26.0-insider
Extension version (available under the Extensions sidebar): 2018.7.0
OS and version: macOS 10.13.6
Python version (& distribution if applicable, e.g. Anaconda): 2.7.15
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pyenv
Relevant/affected Python packages and their versions: XXX

All relative imports within my own code (non-3rd party) are marked as unable to resolve module. Jedi handles the code correctly.

Logs

Starting Microsoft Python language server.
[Info  - 16:18:10] Created Microsoft.PythonTools.Interpreter.Ast.AstPythonInterpreter instance from Microsoft.PythonTools.Interpreter.Ast.AstPythonInterpreterFactory
Initializing for /Users/panda/.pyenv/versions/wellbeingatwork/bin/python
##########Linting Output - flake8##########
##########Linting Output - flake8##########
##########Linting Output - flake8##########
##########Linting Output - flake8##########

[alnvdl]

I got this down to a minimal set of steps:

1. Create a project structure like this

    project
        package
            __init__.py
        test.py
        env
   

   package is a package with an empty __init__.py file. test.py tries to import package. env is a virtual environment (python3 -m venv env)

2. Open this folder in fresh install of VSCode 1.25 and vscode-python 2018.7.0 as a single-folder workspace (just Open folder), with Jedi disabled. Set the Python interpreter to the one in the virtual environment.

3. You’ll see the “IntelliSense may be missing” message for the import package line.

To be honest, the virtual environment doesn’t make a difference, I just included it because it’s one more place to look for the package in addition to the system libs and our own packages, and it isn’t working either. I tested this on Debian 9, but I don’t think it makes a difference (others have different setups). Import, auto-completion and signatures for global packages (e.g.: datetime, json) work just fine.

As I said in my previous message, adding folders manually in python.autoComplete.extraPaths makes it work.