VSCodium start-up error: No module named jedi_language_server

[libreom]

Type: Bug

It just doesnt work anymore
1.Its in windows7, codium https://github.com/Alex313031/codium/releases
if you want logs i can provide
ModuleNotFoundError: No module named 'jedi_language_server'

Extension version: 2023.18.0
VSCodium version: Codium 1.82.2 (adc83b19e793491b1c6ea0fd8b46cd9f32e592fc, 2023-09-23T08:50:37.622Z)
OS version: Windows_NT x64 6.1.7601
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz (4 x 2394)
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 opengl: enabled_on rasterization: unavailable_off raw_draw: disabled_off_ok video_decode: enabled video_encode: unavailable_off vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	3.85GB (1.23GB free)
Process Argv
Screen Reader	no
VM	0%

[karthiknadig]

@libreom What is the versin of python you are using. 2023.18 dropped support for 3.7.

[libreom]

@libreom What is the versin of python you are using. 2023.18 dropped support for 3.7.

Python 3.8.18

[mtreca]

Had a similar issue although my project uses python 3.8. Turns out that the default python interpreter used by VSCode is still python 3.7, which you can observe using which python.

Changing the default startup interpreter to python3.9 fixed the issue for me:

[bkis]

I have the same problem.

• Pop!_OS 22.04 LTS
• VSCodium 1.83.0
• ms-python extension v2023.18.0
• default interpreter is set to python3.10

[PureTryOut]

I can reproduce this error on Arch Linux. My default startup interpreter was for some reason set to a project specific one but even resetting it to the default (which is python which Arch Linux doesn't actually provide, it should at least be python3) or python3.11 didn't fix the problem. I even installed jedi-language-server from the distro repositories (so it at least works with the system-provided Python) but that didn't fix anything either.

Is the extension not supposed to manage it's own version of the language server?

2023.16.0 of the extension works just fine so I guess I'm sticking to that for a while...

[bkis]

Thanks @PureTryOut, I downgraded to ms-python 2023.16.0 and it's indeed working again. For anyone having the same problem - this is a quick temporary fix using the extension's management page:

[libreom]

installing 2023.16.0 fixed the issue for me

[MiltiadisKoutsokeras]

Error occurs in this version too, Debian 11 installation:

Version: 1.83.0
Release: 23283
Commit: 623395426cc947eec9f40b93b17b0ed45d923b66
Date: 2023-10-10T13:34:37.406Z
Electron: 25.8.4
ElectronBuildId: undefined
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Linux x64 5.10.0-26-amd64

Python extension version: v2023.18.0
Python version: 3.9.2

Output of Python Language Server:

2023-10-11 13:30:27.588 [info] Traceback (most recent call last):
  File "/home/langaware/.vscode-oss/extensions/ms-python.python-2023.18.0-universal/pythonFiles/run-jedi-language-server.py", line 9, in <module>
    from jedi_language_server.cli import cli
ModuleNotFoundError: No module named 'jedi_language_server'

2023-10-11 13:30:27.601 [info] [Error - 1:30:27 PM] Server initialization failed.
2023-10-11 13:30:27.601 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097 
2023-10-11 13:30:27.601 [info] [Info  - 1:30:27 PM] Connection to server got closed. Server will restart.
2023-10-11 13:30:27.601 [info] true
2023-10-11 13:30:27.601 [info] [Error - 1:30:27 PM] Python Jedi client: couldn't create connection to server.
2023-10-11 13:30:27.601 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097 

[karthiknadig]

Can you check if the following folder exists? /home/langaware/.vscode-oss/extensions/ms-python.python-2023.18.0-universal/pythonFiles/lib/jedilsp

[karthiknadig]

If possible can some one provide the VSIX or path to the VISX that is used with VSCodium?

[telmop]

Same here. Ubuntu 22.04.

Version: 1.83.0
Release: 23283
Commit: 623395426cc947eec9f40b93b17b0ed45d923b66
Date: 2023-10-10T13:34:37.406Z
Electron: 25.8.4
ElectronBuildId: undefined
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Linux x64 5.15.0-86-generic snap

Edit: it seems to be a problem with 2023.18.0. Downgrading to 2023.16.0 fixed it for me.

[bkis]

Can you check if the following folder exists? /home/langaware/.vscode-oss/extensions/ms-python.python-2023.18.0-universal/pythonFiles/lib/jedilsp

@karthiknadig The folder does indeed not exist (it does when downgrading to 2023.16.0).

[bkis]

If possible can some one provide the VSIX or path to the VISX that is used with VSCodium?

It should be this one.

EDIT: ...and jedilsp is missing in there, too.

[karthiknadig]

This looks like an issue with the python VSIX that was uploaded to Open VSX. I am not sure how it is published there or the build process for Open VSX.

The left is VS Code market place VSIX which has the jedi LSP, the right one is from Open VSX:

[karthiknadig]

Closing this here since it is an upstream issue with how the VSIX was built for VSCodium.

The only change between the previous version of extension and this is that the minimum version of python used is 3.8. I am suspecting the build system is running using 3.7. The latest version of jedi-language-server dropped 3.7, and hence you don't see it in the Open VSX build.

[bkis]

@karthiknadig Thanks for helping to investigate. This makes a lot of sense now. I'm going to try to point someone from open-vsx to this issue, as this problem makes their ms-python build unusable.

I'm just gonna mention the folks from EclipseFdn here, hoping that this reaches the right people somehow. Unfortunately I couldn't find any info on a direct responsibility for the ms-python build.

@mbarbero, @chrisguindon, @oliviergoulet5, could you make this happen? Thanks!

[mbarbero]

Opening EclipseFdn/publish-extensions#714 was the right thing to do. @kineticsquid and/or @filiptronicek can probably follow up with you. Thanks!