Error for py files: `Please install Jedi if you want to use jedi-vim.`
See original GitHub issueInstalled jedi-vim including Jedi using git submodule update --init
from within repo after cloning with clone --recursive
but still unable to get vim to detect jedi-vim whenever I try and open a python file.
Issue Analytics
- State:
- Created 8 years ago
- Comments:17 (1 by maintainers)
Top Results From Across the Web
Autocompletion with Jedi-vim gives Error - Stack Overflow
This is the error that I am getting when I look into the :messages in Vim. Please install Jedi if you want to...
Read more >1190187 – Standard installation of vim-jedi is broken
If I try to open a python file with vim, I get the following error in vim: ... vim.error: Vim(echoerr):Please install Jedi if...
Read more >jedi - PyPI
Jedi is a static analysis tool for Python that is typically used in IDEs/editors plugins. Jedi has a focus on autocompletion and goto...
Read more >Installation and Configuration — Jedi 0.18.2 documentation
Most people will want to install Jedi as a submodule/vendored and not through pip/system wide. The reason for this is that it makes...
Read more >jedi-vim prevents mapping [[ to * and ]] to
Working with the plugin: if you want to get rid of all python specific ... prevention of over-riding plyugin settings in the after...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
trust me, this command will work.
brew install vim --with-lua
I had the same issue. In my case (which may be different), the problem was that I had multiple installations of Python, and vim was detecting the wrong version.
I was able to fix this on OS X 10.10 by recompiling macvim and explicitly declaring the
vi_cv_path_python
variable, which specifies the path to the correct Python binary.Hope this helps someone.