Jedi-vim VS vundle

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

I'm confused. What install guide are you talking about to be specific (as in, please actually send a link)? The official repository is at https://github.com/VundleVim/Vundle.vim and it doesn't mention Python at all. From what I understand Vundle is not written in Python and should not have a dependency to it. If in doubt, consult official documentation rather than third-party tutorials and guides which could be wrong and/or including extra steps that are not necessary.

Vundle https://github.com/VundleVim/Vundle.vim

For example, a link to Git for Windows on Vundle's wiki was replaced with a link to malware:

https://github.com/VundleVim/Vundle.vim/wiki/Vundle-for-Windows/_compare/3aeb22ac39229af4312f2be1052ead184dd5b54d...aa3d293dd18ae1cb4f049c43b73b951651515863

In fact, all five recent edits, made by three different accounts, were malicious:

https://github.com/VundleVim/Vundle.vim/wiki/Vundle-for-Windows/_history

I recommend restricting editing in your GitHub wikis to collaborators only.

## Vundle Install Script function install-vundle() { git clone https://github.com/VundleVim/Vundle.vim.git ~/.vim/bundle/Vundle.vim; sudo gem install vundle-cli; if ! grep -Fxq 'set rtp+=~/.vim/bundle/Vundle.vim' ~/.vimrc then echo "\nset nocompatible\nfiletype off\nset rtp+=~/.vim/bundle/Vundle.vim\ncall vundle#begin()\n\nPlugin 'VundleVim/Vundle.vim'\n\ncall vundle#end()\nfiletype plugin indent on" >> ~/.vimrc; fi }

A typo. I meant vundle. VimBundle