vscode-python: IntelliSense and formatting not working on a fresh install
Environment data
VS Code version: 1.18.1 Python Extension version: 0.8.0 Python Version: 3.6.1 OS and version: macOS Sierra 10.12.6
Actual behavior
I just installed vscode and the python extension. I don’t get any auto completion or auto formatting. I have the following in my settings.json
{
"python.pythonPath": "/Library/Frameworks/Python.framework/Versions/3.6/bin/python3"
}
Expected behavior
Expect to see autocompletion and autosuggestion when I type os.
after import os
.
Steps to reproduce:
-
install vs code on osx
-
install python extension
-
IntelliSense not working
-
I also tried
Python: Select Interpreter
. I getcommand 'python.setInterpreter' not found
.
Logs
Output from Console window
(Help->Developer Tools menu)
shell.ts:459 [ms-python.python] spawn ENOTDIR: Error: spawn ENOTDIR
at exports._errnoException (util.js:1050:11)
at ChildProcess.spawn (internal/child_process.js:319:11)
at exports.spawn (child_process.js:390:9)
at Object.exports.execFile (child_process.js:155:15)
at Object.module.(anonymous function) [as execFile] (ELECTRON_ASAR.js:200:20)
at Promise (/Users/upkar/.vscode/extensions/ms-python.python-0.8.0/out/client/interpreter/locators/services/condaEnvService.js:90:35)
at Promise (<anonymous>)
at CondaEnvService.<anonymous> (/Users/upkar/.vscode/extensions/ms-python.python-0.8.0/out/client/interpreter/locators/services/condaEnvService.js:88:24)
at Generator.next (<anonymous>)
at /Users/upkar/.vscode/extensions/ms-python.python-0.8.0/out/client/interpreter/locators/services/condaEnvService.js:7:71
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 15 (2 by maintainers)
To whoever lands on this issue from Google: Reinstall the extension 😃
@DonJayamanne Isn’t there a way for vscode to loudly complain if an extension is broken and throwing errors in the console, hinting at reinstalling it? It’s a reach for users to jump in the devtools when some extension functionality is not working correctly.
Please could you try reinstalling the extension.