Experiment with Pylyzer as Python language server #48
Comments
|
Downside is that Pylyzer does not appear to support import sorting natively. Maybe this is an acceptable tradeoff. |
|
Pylyzer does not appear to support local package resolution e.g. in virtualenvs (mtshiba/pylyzer#22), which might be a non-starter. |
|
Alternatively, Homebrew/homebrew-core#139195 added several of the optional extensions, e.g. for Black and Mypy, to the Homebrew recipe for python-lsp-server. Let's try using that to install python-lsp-server first and see how things like local package discovery work w/ the Homebrew-installed version. |
jinnovation
added a commit
that referenced
this issue
Mar 28, 2024
This never actually worked. Plus, as noted in #48, the Homebrew recipe for `python-lsp-server` installs several (not all) of my desired extensions alongside the main server itself. Assuming the Homebrew "version" of `python-lsp-server` "works" (e.g. does jump-to-def'n for virtualenv packages as well), then that obviates the need for this bespoke Docker-language-server thing entirely.
|
Closing in favor of #49. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Historically have used python-lsp-server. For whatever reason (maybe misconfiguration on my part?) this has always required me to reinstall the language server package on each virtualenv that I set up for my projects (otherwise stuff like jump-to-def doesn't work). To make things worse, I've always needed to install all companion "extensions" to the language server as well, including:
This is extremely cumbersome past a small handful of Python codebases.
Pylyzer looks like a promising alternative that might have a less finicky install story. If that proves to be the case, replace current use of python-lsp-server with that.
The text was updated successfully, but these errors were encountered: