search

davidhalter / jedi-vim

Using the jedi autocompletion library for VIM.
MIT License
5.27k stars 370 forks source link

Vim freezing when opening python file #998

Closed wviana closed 3 years ago

wviana commented 4 years ago

Issue

I'm currently unable to use jedi, cause sometime to now every time I do open a python file with it enabled it got stuck.

Currently I've tried to open vim with vim -V --noplugins and than source the ~/.vim/plugged/jedi-vim/autoload/jedi-vim.py

Got this output 

chdir(/Users/wviana/.vim/plugged/jedi-vim/autoload)
fchdir() to previous dir
sourcing "/Users/wviana/.vim/plugged/jedi-vim/autoload/jedi.vim"
Error detected while processing function jedi#init_python[4]..<SNR>17_init_python[27]..jedi#setup_python_imports:
line   25:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "<string>", line 8, in <module>
ImportError: No module named jedi_vim_debug
finished sourcing /Users/wviana/.vim/plugged/jedi-vim/autoload/jedi.vim
Press ENTER or type command to continue
wviana commented 4 years ago

After more test and reasearch I'm pretty sure it's because my system have just python3.8, and looks like macvim does not support it. I'm thinking about keeping two versions, but really missing GNU/Linux right now.

davidhalter commented 4 years ago

Hmmm from time to time we get weird error messages like this one for Mac users. Sometimes it's just a broken VIM installation. Some people just install a new VIM version from brew or whatever. Did you try that?

blueyed commented 4 years ago

@wviana Try running the Python code per line manually: https://github.com/blueyed/jedi-vim/blob/76633a57837021c2d813dc1d23d889a88058844f/autoload/jedi.vim#L163-L172

Probably import jedi_vim fails already (and we fail then because we also try to import jedi_vim_debug then. Also try/see if it works with :py3 vs :py etc.

blueyed commented 4 years ago

OTOH it looks like this for me, i.e. it includes the first error (py3 though only):

Error detected while processing function jedi#init_python[4]..<SNR>131_init_python[27]..jedi#
setup_python_imports:
line   26:
Traceback (most recent call last):
  File "<string>", line 3, in <module>
ModuleNotFoundError: No module named 'jedi_vimmm'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "<string>", line 8, in <module>
ModuleNotFoundError: No module named 'jedi_vim_debuggg'

You might want to try https://github.com/davidhalter/jedi-vim/pull/1000.

wviana commented 4 years ago

I didn't solve it in vim, but had migrated into NeoVim, there just installing pynvim package the neovim had found the python 3.8. So no I'm a Neovim user.

davidhalter commented 3 years ago

I'm pretty sure that this was an issue with VIM itself and not jedi-vim, since nobody else had this. I'm closing. Feel free to report again if this is an issue with a proper new installation of VIM/Python.