python-lsp-server

1. https://docs.astral.sh/ty/ 2. https://github.com/microsoft/pyright 3. https://github.com/python-lsp/python-lsp-server 4. https://github.com/palantir/python-language-server

https://peps.python.org/pep-0810/#what-about-star-imports-fr... > What about star imports (`from module import *`)? > Wild card (star) imports cannot be lazy - they remain eager. This is because the set of names being imported cannot be determined without loading the module. Using the lazy keyword with star imports will be a syntax error. If lazy imports are globally enabled, star imports will still be eager. Additionally, star imports can interfere with type checkers and IDEs and shadowing caused by star imports is a frequent and difficult to diagnose source of bugs (you analyze the function you think you're calling and find no issues, but you're actually calling a different function because the star import occurs after your explicit import). You might be able to workaround this limitation by doing a lazy import into an intermediate modu

Python LSP Server works great, is easier to install and even offers some optional extensions. https://github.com/python-lsp/python-lsp-server

I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager use it to install the rest of your plugins. These two plugins are the bare minimum in my view. https://github.com/nvim-treesitter/nvim-treesitter Treesitter gives you much better syntax highlighting based on a parser for a given language. It's much more robust than the regex-based default highlighting. https://github.com/neovim/nvim-lspconfig This plugin helps you connect to a given language LSP quickly with sensible defaults so you can get IDE features. You'll still need to install the LSP though. https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser... For Python you'll want pylsp. For JavaScript

I came in at the tail end of https://github.com/python-lsp/python-lsp-server/issues/195. The possibility of me sponsoring a fix came up, and I’m on board with it, but the other contributor never replied.

Have you opened an issue against https://github.com/python-lsp/python-lsp-server? I'm an occasional contributor for easy fixes; if your fix is easy chances are it would get picked up.

You have to tell the server how to interpret the code somehow. I mentioned line length. In Python, you may want one configurable max for code and another for comments. If you can pass those to the server, it can tell you which lines are too long using the standard mechanism for identifying errors and warnings. Otherwise, the editor would have to know how to parse the code so it could know whether a given line is code or comment. That’s the sort of thing LSP can do better. That’s just one example, not the lone thing users would likely configure. Edit: More concretely, here are some of the config knobs you can twiddle via LSP for the particular server I’ve been discussing: https://github.com/python-lsp/python-lsp-server/blob/develop... There are other plugins around with settings that aren’t documented there, but are still configured throug

Just use the open source python LSP that is written in Python and maintained by the Spyder IDE team. https://github.com/python-lsp/python-lsp-server Someone might come along and tell you that you are missing out on some pylance features, but fuck closed source dev tooling it ain't worth it.

This has not been my experience. For example I use this python language server, which is implemented in Python and uses jedi: https://github.com/python-lsp/python-lsp-server Rust analyzer is written in Rust, gopls in Go, clangd in C++, R language server in R, Jsonnet language server in Go, sqls in Go.

> And neovim is heavily embracing the LSP paradigm, where you'd use something like gd to jump to definition when on top of a function and a language specific LSP server will tell Neovim where to jump to. This x100. I switched to neovim+pylsp a few months ago, and it's been an absolute delight. I use lspconfig [1] and pyslp [2] since most of my time is spent developing Python code. Not only can I navigate more quickly and easily, I also find myself catching more silly errors before run-time due to better linting from the lsp. It used to be that I wouldn't use vim beyond quick edits on single files. Although I still prefer to use vim style bindings in IDEs, I can go much further before I feel the need to fire up an IDE in the first place. [1]: https://github.com/neovim/nvim-lspconfig [2]: https://github.com/python-lsp/python-lsp-server