Jedi-vim VS pydoc.vim

jedi-vim does autocomplete, docstring/signature/stub lookup, usage finding, bulk renaming...

The readme for jedi-vim says it works with Python 3:

To be able to use ctags you have to run ctags in the source directory to generate the index files. But a better way is to just modify the keywordprg when in a Python buffer or even better use a plugin like pydoc.vim or jedi-vim

I added https://github.com/davidhalter/jedi-vim to my plugins in ~/.config/nvim/init.vim and ran PlugInstall and it worked, but whenever I try to open a python file and the autocomplete part should come up I get

But LSP is a critical part of my Python setup, where I use David Halter's jedi-vim for completion, renaming, go-to-definition, finding usages of variables, etc., so I'm definitely not opposed to LSP on principle. I guess I just found Latex wasn't a complicated enough language for me to benefit from the full suite of features an LSP provides.

Install linux (WSL) with this tutorial (assuming you are on windows) and go through this tutorial to get used to it. To write python scripts, use vim and install this plugin.

I think you can get that behavior with https://github.com/davidhalter/jedi-vim but I haven't tried it.

Firstly I will like to install Jedi for code completion in Python. The plugin can be simple and straightforward to install using any of the above plugin managers. Jedi-Vim provides some neat and clean** syntax analytics and autocompletion for Python in Vim**. You'll find the docs and installation process here JEDI-VIM

I've never used it, not really a python gal, but from what I read, jedi sounds like a good one (https://github.com/davidhalter/jedi-vim).

See https://github.com/davidhalter/jedi-vim

And the big advantage of using something like pydoc.vim (at least in somini’s fork) is that it will detect the right python version and try to use your imports to look up the correct pydoc page.

K is nice, but usually plugins that remap it are better than setting keywordprg. For example, somini/pydoc.vim opens the help in a vim buffer* so you can read the help while you edit your code. Same for the built-in man plugin (mirror).