Experiment with Pylyzer as Python language server
jinnovation opened this issue · comments
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.
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.
Closing in favor of #49.