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
Error detected while processing youcompleteme.vim #2124
Comments
This is not an issue with YCM but Vim not able to find Python on your system. You can confirm this by trying to run the command (for Python 2): :py print('test') inside Vim. You should get the same error message. Now, we need to understand why Vim can't find Python 2 or 3. First, what is the output of the following commands in Vim: :echo has('python')
:echo has('python3') ? |
Hello. I have the same issue. In my case
|
If you run vim with If it doesn't work (you still get an error), then this is clearly not a YCM issue, and an issue with your installation of Vim and Python,. |
@Cemenyave Which version of Python 2 are you using? I think you are experiencing this Python 2.7.11 issue. |
@micbou, thank you! That helped. |
I had this problem with |
I tried every conceivable combination of installing Python and Vim on my MacBook using brew and nothing worked. For some reason the following did:
Check installation:
Above comes from Vim, YouCompleteMe and Python - making it work by Oliver Schrenk. Hope that helps some of you! |
I'm running Windows 10, 64 bit Vim, 64 bit Python version 3.5.1.
I get the following error message every time I run Vim:
I've tried setting the g:ycm_path_to_python_interpreter as well as the g:ycm_python_binary_path to no avail. I've tried using 2.7.11 and 2.7.9 versions of python. There are no logs saved within %TEMP%/ycm_temp.
I am currently using this _vimrc:
I compiled the ycm_core using MSVC 14 and using
python install.py --clang-complete
which ran successfully with no errors.I have only one version of python installed, with Vim installed from a recent build from micbou's bintray.
The text was updated successfully, but these errors were encountered: