Intellisense Issue
See original GitHub issueIssue Type: Bug
Behaviour
Expected vs. Actual
Python Extension giving syntax errors for perfectly fine code. For a statement like def function_name():, it shows a syntax error. After the latest update, the intellisense does not seem to be working.
Steps to reproduce:
- Tried restarting VS Code several times. Also tried deleting and re-installing VS Code. No change. Tried disabling and uninstalling the extension as well.
I use VS Code with WSL, and the intellisense does not work with the normal powershell as well.
Steps to reproduce:
- XXX
Diagnostic data
- Python version (& distribution if applicable, e.g. Anaconda): 3.8.10
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
- Value of the
python.languageServer
setting: Jedi
User Settings
defaultLS: {"defaultLSType":"Pylance"}
downloadLanguageServer: true
envFile: "<placeholder>"
venvPath: "<placeholder>"
venvFolders: "<placeholder>"
condaPath: "<placeholder>"
pipenvPath: "<placeholder>"
poetryPath: "<placeholder>"
languageServer: "Jedi"
linting
• enabled: true
• cwd: "<placeholder>"
• Flake8Args: "<placeholder>"
• flake8Enabled: false
• flake8Path: "<placeholder>"
• lintOnSave: true
• banditArgs: "<placeholder>"
• banditEnabled: false
• banditPath: "<placeholder>"
• mypyArgs: "<placeholder>"
• mypyEnabled: false
• mypyPath: "<placeholder>"
• pycodestyleArgs: "<placeholder>"
• pycodestyleEnabled: false
• pycodestylePath: "<placeholder>"
• prospectorArgs: "<placeholder>"
• prospectorEnabled: false
• prospectorPath: "<placeholder>"
• pydocstyleArgs: "<placeholder>"
• pydocstyleEnabled: false
• pydocstylePath: "<placeholder>"
• pylamaArgs: "<placeholder>"
• pylamaEnabled: false
• pylamaPath: "<placeholder>"
• pylintArgs: "<placeholder>"
• pylintPath: "<placeholder>"
sortImports
• args: "<placeholder>"
• path: "<placeholder>"
formatting
• autopep8Args: "<placeholder>"
• autopep8Path: "<placeholder>"
• provider: "autopep8"
• blackArgs: "<placeholder>"
• blackPath: "<placeholder>"
• yapfArgs: "<placeholder>"
• yapfPath: "<placeholder>"
testing
• cwd: "<placeholder>"
• debugPort: 3000
• nosetestArgs: "<placeholder>"
• nosetestsEnabled: undefined
• nosetestPath: "<placeholder>"
• promptToConfigure: true
• pytestArgs: "<placeholder>"
• pytestEnabled: false
• pytestPath: "<placeholder>"
• unittestArgs: "<placeholder>"
• unittestEnabled: false
• autoTestDiscoverOnSaveEnabled: true
terminal
• activateEnvironment: true
• executeInFileDir: "<placeholder>"
• launchArgs: "<placeholder>"
experiments
• enabled: true
• optInto: []
• optOutFrom: []
tensorBoard
• logDirectory: "<placeholder>"
Extension version: 2022.4.1 VS Code version: Code 1.66.1 (8dfae7a5cd50421d10cd99cb873990460525a898, 2022-04-06T14:50:12.141Z) OS version: Windows_NT x64 10.0.22000 Restricted Mode: No Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2
System Info
Item | Value |
---|---|
CPUs | Intel® Core™ i5-9300H CPU @ 2.40GHz (8 x 2400) |
GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
Load (avg) | undefined |
Memory (System) | 7.88GB (1.18GB free) |
Process Argv | –crash-reporter-id 68883325-959a-43a0-af1c-41f9748d77a0 |
Screen Reader | no |
VM | 0% |
Item | Value |
---|---|
Remote | WSL: Ubuntu |
OS | Linux x64 5.10.16.3-microsoft-standard-WSL2 |
CPUs | Intel® Core™ i5-9300H CPU @ 2.40GHz (8 x 2400) |
Memory (System) | 3.78GB (3.00GB free) |
VM | 0% |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
pynewfile477:30463512
Issue Analytics
- State:
- Created a year ago
- Comments:21 (7 by maintainers)
Top Results From Across the Web
IntelliSense not working in VS Code - The Windows Club
If IntelliSense or Autocomplete is not working in Visual Studio Code on your computer, the recommended fixes in this post are sure to...
Read more >Visual Studio IntelliSense Not Working? What To Do.
Visual Studio IntelliSense Not Working? What To Do. · Workaround #1: Restart Visual Studio. Yeah, I know. · Workaround #2: Restart Your Machine....
Read more >Visual Studio IntelliSense Not Working? Multiple Ways for You!
Is IntelliSense not working in Visual Studio or Visual Studio Code? Take it easy and try multiple ways here to fix this issue...
Read more >How To Solve IntelliSense Not Working In VS Code
If the IntelliSense is installed and still not working then most of the time restarting/reloading the program will solve the issue.
Read more >Intellisense not working · Issue #110145 · microsoft/vscode
Issue Type: Bug In the October 2020 release, intellisense stops working when the file system changes (e.g. a new file is created, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ll try switching it up. I will post the update here after switching, and then I am gonna close this issue.
Thanks for all the assistance. I’ll post it over there ASAP
@karthiknadig
I think I figured out the issue. I have too many files and folders in my directory. I tried opening another remote WSL window and it works there. So, I am assuming that to be the issue.
Thanks for all the assistance.