YouCompleteMe works great for C/C++. Not so great for python (socket library)

[KraneBrain]

I've been extensively using YouCompleteMe for my C/C++ and I'm loving it. Truly fantastic.

I recently began python development and I feel like it's not nearly as impressive. For example in the below snippet

import socket
import sys

Create a TCP/IP socket

sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
sock.

There's no available autocomplete terms for sock functions such as connect, setblocking, recv, etc...

Is there something I'm doing wrong? The logs appear fine and there is certain autocompletion for most of python (such as time.sleep). It's also able to GoTo the socket library.

[vheon]

I've just tried and I get all the completion. The thing is that jedi at the first call for completion is a little slow but after that it caches all it needs and it starts giving you completion (whenever it can). It doesn't show completion even if you force it with <C-Space>?

[micbou]

@KraneBrain What's the output of the :YcmDebugInfo command when editing your Python file? I think your issue is related to davidhalter/jedi#826.

[KraneBrain]

I apologize for the delay
@vheon yes even with <C-Space> it doesn't auto fill.

@micbou here is the log

Printing YouCompleteMe debug information...                                                                                                                                                                 
-- Client logfile: /tmp/ycm_5IThGb.log                                                                                                                                                                      
-- Server has Clang support compiled in: True                                                                                                                                                               
-- Clang version: clang version 3.9.0 (tags/RELEASE_390/final)                                                                                                                                              
-- Python completer debug information:                                                                                                                                                                      
--   JediHTTP running at: http://127.0.0.1:44091                                                                                                                                                            
--   JediHTTP process ID: 7752                                                                                                                                                                              
--   JediHTTP executable: /home/testing/.vim/bundle/YouCompleteMe/third_party/ycmd/third_party/JediHTTP/jedihttp.py                                                                                         
--   JediHTTP logfiles:                                                                                                                                                                                     
--     /tmp/jedihttp_44091_stdout_aTPbrv.log                                                                                                                                                                
--     /tmp/jedihttp_44091_stderr_gzVNFK.log                                                                                                                                                                
--   Python interpreter: /usr/bin/python                                                                                                                                                                    
-- Server running at: http://127.0.0.1:36112                                                                                                                                                                
-- Server process ID: 7709                                                                                                                                                                                  
-- Server logfiles:                                                                                                                                                                                         
--   /tmp/ycmd_36112_stdout_DdQO_g.log                                                                                                                                                                      
--   /tmp/ycmd_36112_stderr__1Vt6g.log                                                                                                                                                                      
Press ENTER or type command to continue 

[micbou]

Are you getting the same completions as the ones in this screenshot?

[KraneBrain]

@micbou
Here is a picture of what you sepcified. Also, here's a list of what's NOT in the list

next
dict
long
module
native
nonzero
unicode
weakref

Why do you (and me) not have connect?

[vheon]

@KraneBrain what happen if you type c or co?

EDIT: actually I tried again and I don't have connect either, so at this point I think is a problem with jedi itself.

[KraneBrain]

@vheon Thank you for confirming. Should I reach out to the jedi group about the issue?

[micbou]

Jedi author doesn't seem to be interested in fixing the issue and recommend to use Python 3 in that case.

@vheon We could directly implement the fix in JediHTTP by adding the socket module to the auto_import_modules option on Python 2.

[vheon]

@micbou I saw that you asked on jedi's tracker about adding socket to auto_import_modules. I'm fine if we want to patch it JediHTTP but do we want to wait and see if they include it upstream first? We could also just put it in JediHTTP and remove it if they merge it upstream.

[puremourning]

I think this is fixed upstream now and just needs the JediHTTP module updating ? Can someone confirm?

[micbou]

Yes but JediHTTP was updated with a version of Jedi that doesn't pass the ycmd tests because of some docstring issues. They are fixed in Jedi dev branch (see PRs davidhalter/jedi#941 and davidhalter/jedi#942) and we are now waiting for these fixes to be included in the master branch.