I’m trying the CodeLLDB extension which is great. Finally we can debug C++ code without Visual Studio on Windows.
(This extension was inspired by Are We IDE yet project but it actually benefits C++ a lot.)
However the typing support for lldb package is not there. That means I can’t use auto-complete when authoring a debugger script.
So I created a typing package: lldb-typeinfo.
Then I noticed that there are color differences between Jedi and Pylance:
(Is Microsoft doing this on intension? there are already existing issue and they are not interested in it…)
I tried to fix the Jedi extension, and it might be easy, because someone already implemented it in kylin-python and there is a pull request for python-lsp-server.
However I’m struggling with the packaging process. such as file name too long, and it even have a Rust dependency…
After much trouble I’m able to package it, (and find out how it installs the python packages), I’m still get an error for a npm package not found after installed it…
Well I have no choice but to switch to the official version.
It seems that pylance was good, but it’s only good at color. the docstrings are missing compared to jedi:
So the python support is actually broken.
Well it might be still better than Ruby, which isn’t even usable now, but I wonder if I should switch to a more lsp-usable language, such as Go or Rust…
Help on implementation
vscode semantic hightlighting example
how it install python packages
python -m pip install -t ./python_files/lib/jedilsp --no-cache-dir --implementation py --no-deps --require-hashes --only-binary :all: -r ./python_files/jedilsp_requirements/requirements.txt
(this step is invoked via nox. See the github action for build-vsix.)
the installed packages can be found at python_files\lib directory: