Closed stu105502 closed 5 years ago
Thanks
No problem, btw the docstring-function seems to be able to receive an optional parameter called 'raw'. If you use completion.docstring(raw=True), jedi does not processes signatures and return the plain docstring without additional information. This does no help with the snippet-generation but at least, this would always produce a docstring you could show.
The jedi library seems to have for the time being general problems with its signature class. You are explicitly catching these exceptions in your lines 73-83
and have noticed this problem but jedi seems to have the tendency to use signatures and repeat an assertion-error regarding some binding mechanism when you call docstring on certain completions. I don't know what the error of jedi is but because of it my autocompletion regarding numpy does never work and stops ncm2-jedi completely. With python3 these signature problems are produced by some star-parsing, while in python2 some binding problems occur. By simply using try/except blocks for the dockstrings one can avoid these signature errors until these problems are fixed and contain ncm2-jedi functionality.
Maybe you can replicate the assertion error to by simply running this python code:
in my case jedi fails always with python2 as well python3