Intellisense isn't working at all

[trondhindenes]

Environment data

VS Code version: 1.19.1
Python Extension version: 0.9.1
Python Version: 3.6.3
OS and version: Ubuntu 17.10

Actual behavior

I'm not getting any intellisense in Python files. The linter is working as expected, and VSCode shows the "python version selector" so the plugin itself is loaded and all that. But there's not intellisense, apart from "dumb" autocomplete based on keywords/code already in the file. Ctrl+Space only produces "generic" suggestions.

Expected behavior

Intellisense should like it doesn in other IDEs

Steps to reproduce:

Logs

Output from Python output panel

I don't know what the python output panel is

Output from Console window (Help->Developer Tools menu)

/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:2571 [Extension Host] debugger listening on port 9333
/usr/share/code/resources/app/out/vs/workbench/workbench.main.js:2569 [Extension Host] debugger inspector at %cDebugger listening on port 9333.
Warning: This is an experimental feature and could change at any time.
To start debugging, open the following URL in Chrome:
    chrome-devtools://devtools/bundled/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:9333/cf67e832-ca46-4d9a-bfee-c1cd26da656e

[brettcannon]

Or you attempting this with just a file open or did you open a workspace? And did you make sure you selected a Python interpreter? Intellisense only works when you specify an interpreter, not simply having the option to select one.

(And FYI, the "Python output panel" is what you get when you go to View -> Output and then change the dropdown to Python).

[MikhailArkhipov]

Might be addressed by #536

[MikhailArkhipov]

Closing with #536, please check in the next update (Jan 2018+)

[trondhindenes]

Thanks, waiting for the next update.

This is when a folder containing a python app is open. The Python output is just showing linter information. from pylint.

When I hit Ctrl+Space inside a method there's a super-brief "waiting" label being shown (barely visible) before vscode shows "generic" information. If I just stop and wait after the opening paranthesis of the method call vscode correctly shows the available method arguments. It is my impression that ctrl+space would allow "tab-completion" of the valid arguments (at least thats how other IDEs i've been using works). I also notice that typing the first character of an argument name will allow me to tab-complete that argument.

There's a good chance that vscode's python intellisense works as intended and that the behaviour is just different (not as sophisticated in some situations) from other IDEs.

I'm fine with us closing this issue.

[brettcannon]

@trondhindenes if you want to help us test that this is fixed, please try out an insiders build of the extension.

[trondhindenes]

sweet, I'll install that right away and give it a whirl!

[brettcannon]

@trondhindenes were you able to ever try out an insiders build of the extension to validate our fix for you?