Python-Lsp-Server as a replacement for Jedi-Language-Server

[dasTanmoy0096]

Why does this extension use the much featureless Jedi-Language-Server? Considering much of the upstream work happens on Python-Lsp-Server, which is maintained by the Spyder-IDE Team, it is rather weird to not use the LSP that recieves more attention and features.

One of the especially better features of Python-Lsp is that it features inbuilt Docstring to Markdown. Jedi and Jedi-LSP both are notorious for showing insanely long document hovers for docstrings, Python Lsp seems to fix that by using it's own in-house solution.

Not to mention the supporting extensions such as Black, Isort, MyPy, etc. is kinda unnecessary cause Python-Lsp integrates them from the get go.

Any future plans to drop Jedi and instead use PyLsp?

[karthiknadig]

@dasTanmoy0096 for tooling like linting, formatting, and import sorting, I recommend using the Ruff Extension. Ruff provides a high-performance, all-in-one solution that covers most rules from multiple linters (pylint, flake8, mccabe, many more), and it’s actively evolving. They are also working on a static type-checker, making it a strong candidate for modern Python tooling.

Regarding docstring formatting, jedi-language-server does use docstring-to-markdown. If the hover tooltips are excessively large, that sounds like a bug worth reporting to jedi-language-server.

The Python ecosystem is rapidly evolving, and we are continuously evaluating the best tools to use. While jedi has limitations, the alternative (PyLsp) also relies on jedi under the hood. Given the emergence of modern, high-performance tools, we might consider adding support for natively built servers or exposing an API that allows any server to be used.