-
-
Notifications
You must be signed in to change notification settings - Fork 370
-
-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jedi 0.6 Version too old? #134
Comments
After adding the followings to my .vimrc,
The errors from ftplugin/python/jedi.vim are gone. But other errors still persist. |
I forgot to update the jedi sub repository in @brownianwalker The way vundle works is that it checks out the repository and all sub repositories. This leaves the jedi pip version unused. Are your commands above still relevant after this bug fix? I think you can just remove them. |
Thank you for you prompt response. Unfortunately, it still does not work for me. I tried to manually clone the repository, switch to dev branch and update its jedi submodules using the following commands, but the errors remain the same. Any idea?
|
At least the Can you tell me a little bit more about your operating system (distro, version) and tell me the output of |
I am using Linux Mint 14, MATE 1.4.2. gvim 7.3. The ver output is as followings,
|
That is really strange! I have no idea what the problem could be. Basically it looks like the definitions in Of course you could always try to recompile and so on. But the version looks fine. Maybe you could also create a vim.log of the startup. I don't know how to do that anymore. But that could help. |
I tried to install only jedi-vim without any other plugins, configuration options and bundle manager. It works properly. I thought it was due to my configuration. I disabled plugins and turned off the configuration options from my vimrc one by one and at last it turns out to be a configuration option I used to detect file type.
After removing this line, it works. As I am not familiar with the internals of vim, I am not sure how it is affecting the plugin. But at least it is working now. Thank you for this awesome plugin and I am sorry that I should have verified the bug at the beginning. |
After further testing, I found that removing "filetype detect" will make my other plugins failing to work properly. As I mentioned I am not familiar with vim internals, I am clueless about what is happening. |
Strange. Maybe jedi-vim/YouCompleteMe don't play nice together? We are in the progress of making them play nicely together. |
I am currently not using YouCompleteMe although I am exploring to replace my clang_complete with it. The link I referenced contains the setting to configure supertab and clang_complete for argument completion. So the error should not be related to YouCompleteMe. |
I think I use |
I have both "filetype plugin" and "filetype detect" on. Anyway, thank you for your help. |
Just wanted to mention that YouCompleteMe and jedi-vim do not play nice together (YouCompleteMe and Jedi OTOH play very nice together; YCM uses Jedi as a git submodule). You'll have to pick one or the other; since YCM uses the same Jedi library as the semantic backend for Python, it's not really that much different. There are a few minor features present in jedi-vim that YCM currently does not have (see #119), but they will be added in the near future. Also, YCM has a ton of features not present in jedi-vim, so for now you'll have to pick which ones are more important to you. |
I managed to solve the issue by moving the declaration of jedi-vim bundle after the "filetype detect", inside the python specific block of my vimrc. Just thought it might be useful if anyone else encountered the same issue. |
Hi!
I tried to install jedi and jedi-vim on gvim 7.3, however, whenever I open up a python file, the following errors comes up. The completion seems working properly but I am not sure these errors has any impact. I downloaded the plugin using Vundle and installed jedi 0.6 using pip.
I wonder whether anyone else encountered this problem? Thanks!
The text was updated successfully, but these errors were encountered: