Please complete these steps and check these boxes (by putting an x inside
the brackets) _before_ filing your issue:
vim --version.:YcmDebugInfo.:YcmToggleLogs command.vim -Nu /path/to/YCM/vimrc_ycm_minimal, including what Iinstall.py (or cmake/make/ninja) including its invocationThank you for adhering to this process! It ensures your issue is resolved
quickly and that neither your nor our time is needlessly wasted.
Provide a clear description of the problem, including the following key
questions:
so, what is the recommended way of building ycm after pulling from master?
python completer works
It does not find a python completer.
prompts: ycm-core/YouCompleteMe/third_party/ycmd/ycmd/server_state.py", line 91, in GetFiletypeCompleter
raise ValueError(
ValueError: No semantic completer exists for filetypes: ['python']
Reproduce the issue with
vim -Nu /path/to/YCM/vimrc_ycm_minimal, which
enabled debug logging and other useful diagnostics. Include a link to a
gist containing all of the log files listed by:YcmToggleLogs.
MacOS 10.15
No error reported.
This is a "known" issue that affects some people when switching python versions. It seems to be a problem with Jedi. We're not sure why this happens, but we don't think there's anything that we can do about it. It's something to do with .pyc files.
The solution is to delete the python cached files in Jedi.
cd /path/to/YCM/third_party/ycmdfind . -type f -name '*.pyc' -deleteThen just restart vim.
Let us know if that doesn't fix it for you. Closing as I think this is the solution and I've updated the FAQ to point to it.
I just encountered the problem. The first solution using git clean -xdf didn't help. The second (more adventurous) solution fixed the problem for me.
I just encountered the problem. The first solution using
git clean -xdfdidn't help. The second (more adventurous) solution fixed the problem for me.
Same for me.
I updated the nuclear instructions. but thanks for the info. going to lock this so that the solution doesn't get swallowed.
Most helpful comment
This is a "known" issue that affects some people when switching python versions. It seems to be a problem with Jedi. We're not sure why this happens, but we don't think there's anything that we can do about it. It's something to do with
.pycfiles.The solution is to delete the python cached files in Jedi.
cd /path/to/YCM/third_party/ycmdfind . -type f -name '*.pyc' -deleteThen just restart vim.