From b3b8350fd1b74a422186707bcb57975af684da25 Mon Sep 17 00:00:00 2001 From: Daniel Hahler Date: Wed, 16 Aug 2017 12:54:21 +0200 Subject: [PATCH] README: improve FAQ for slowness, add deoplete-jedi Ref: https://github.com/davidhalter/jedi/issues/910#issuecomment-322731875 --- README.rst | 28 +++++++++++++++++++++------- 1 file changed, 21 insertions(+), 7 deletions(-) diff --git a/README.rst b/README.rst index 0bf10fdd..5a79b3ab 100644 --- a/README.rst +++ b/README.rst @@ -221,16 +221,30 @@ Don't even think about changing the Jedi command to ````, use `supertab `_! -The completion is waaay too slow! ---------------------------------- +The completion is too slow! +--------------------------- + +1. Completion of complex libraries (like Numpy) should only be slow the first + time you complete them. After that the results should be cached and very fast. + +2. If it is still slow after the initial completion and you have installed the + python-mode Vim plugin, try disabling its rope mode: + + .. code-block:: vim -Completion of complex libraries (like Numpy) should only be slow the first time -you complete it. After that, the results should be cached and very fast. + let g:pymode_rope = 0 -If it's still slow, in case you've installed the python-mode VIM plugin, disable -it. It seems to conflict with jedi-vim. See issue `#163 -`__. + See issue `#163 `__. +3. You can also use `deoplete-jedi `__ + for completions, which uses Jedi, but does completions asynchronously + (requires Neovim). + It makes sense to use both jedi-vim and deoplete-jedi, but you should disable + jedi-vim's completions then: + +.. code-block:: vim + + let g:jedi#completions_enabled = 0 Testing =======