Repository navigation
Python Jedi couldn’t connect to Python Language Server #22610
Copy link
Copy link
Closed as not planned
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from posterIssue requires more information from postertriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
Description
Type: Bug
I'm running VS code version 1.85.0 on Windows 11. You can see my report at this website: https://discuss.python.org/t/python-jedi-wont-connect-to-python-language-server/40512?u=coderdjjd
I also found a much needed error log:

Extension version: 2023.22.0
VS Code version: Code 1.85.0 (af28b32d7e553898b2a91af498b1fb666fdebe0c, 2023-12-06T20:48:09.019Z)
OS version: Windows_NT x64 10.0.22631
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Pentium(R) Gold 7505 @ 2.00GHz (4 x 1997) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 7.80GB (2.00GB free) |
| Process Argv | --crash-reporter-id 90aa4b7b-cc80-4d95-8289-dd6215474c6f |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263:30899288
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
282f8724:30602487
f6dab269:30613381
showlangstatbar:30737416
962ge761:30917236
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
welcomedialogc:30910334
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixt:30902429
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
aa_t_chat:30882232
### Tasks
- [ ] https://github.com/microsoft/vscode-python/issues/11812
- [ ] https://github.com/microsoft/vscode-python/issues/21265
### Tasks
- [ ] https://github.com/microsoft/vscode-python/issues/20117
- [ ] https://github.com/microsoft/vscode-python/pull/22132
- [ ] https://github.com/microsoft/vscode-python/pull/22466
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from posterIssue requires more information from postertriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
Activity
CoderDJJD commentedon Dec 9, 2023
Found another error log:

karthiknadig commentedon Dec 13, 2023
CoderDJJD The error seems to be
EACCESSwhich usually means you don't have permissions to run from that executable or that file. Can you please provide details on which path you have used to select python?Also, you can set language server to
Pylanceusingpython.languagServersetting.CoderDJJD commentedon Dec 13, 2023
karthiknadig commentedon Dec 13, 2023
If you switch to using pylance you should not see the error with Jedi. Make sure you use pylance as the language server and it should work as expected. Please share exact error from Output > Python Language server if you see something failing again.
github-actions commentedon Jan 12, 2024
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!