by davidhalter

davidhalter / jedi-vim

Using the jedi autocompletion library for VIM.

4.6K Stars 371 Forks Last release: Not found MIT License 862 Commits 5 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

.. image::

jedi-vim - awesome Python autocompletion with VIM

.. image:: :target: :alt: Travis-CI build status

jedi-vim is a VIM binding to the autocompletion library


Here are some pictures:

.. image::

Completion for almost anything (Ctrl+Space).

.. image::

Display of function/class bodies, docstrings.

.. image::

Documentation (Pydoc) support (with highlighting, Shift+k).

There is also support for goto and renaming.

Get the latest from



Documentation is available in your vim:

:help jedi-vim
. You can also look it up
on github 

You can read the Jedi library documentation


If you want to report issues, just use the github issue tracker. In case of questions about the software, please use

_ and tag your question with


We love Pull Requests! Read the instructions in


The Jedi library understands most of Python's core features. From decorators to generators, there is broad support.

Apart from that, jedi-vim supports the following commands

  • Completion
  • Goto assignment
    (typical goto function)
  • Goto definition
    (follow identifier as far as possible, includes imports and statements)
  • Goto (typing) stub
  • Show Documentation/Pydoc
    (shows a popup with assignments)
  • Renaming
  • Usages
    (shows all the usages of a name)
  • Open module, e.g.
    :Pyimport os
    (opens the



You need a VIM version that was compiled with Python 2.7 or later (

). You can check this from within VIM using
:python3 import sys; print(sys.version)
for Python 2).

Manual installation

You might want to use

_ or
_ to install jedi-vim.

The first thing you need after that is an up-to-date version of Jedi. Install

git submodule update --init --recursive
in your jedi-vim repository.

Example installation command using Pathogen:

.. code-block:: sh

git clone --recursive ~/.vim/bundle/jedi-vim

Example installation using Vundle:

Add the following line in your


.. code-block:: vim

Plugin 'davidhalter/jedi-vim'

For installing Jedi,

pip install jedi
will also work, but you might run into issues when working in virtual environments. Please use git submodules.

Installation with your distribution

On Arch Linux, you can also install jedi-vim from official repositories as

. It is also available on
Debian (≥8) 
Ubuntu (≥14.04) 
__ as vim-python-jedi. On Fedora Linux, it is available as

Please note that this version might be quite old compared to using jedi-vim from Git.


Note that the

_ VIM plugin seems to conflict with jedi-vim, therefore you should disable it before enabling jedi-vim.

To enjoy the full features of jedi-vim, you should have VIM >= 7.3, compiled with

(which is not the case on some platforms, including OS X). If your VIM does not meet these requirements, the parameter recommendation list may not appear when you type an open bracket after a function name. Please read
the documentation 
_ for details.


Jedi is by default automatically initialized. If you don't want that I suggest you disable the auto-initialization in your


.. code-block:: vim

let g:jedi#auto_initialization = 0

There are also some VIM options (like

and key defaults) which are automatically initialized, but you can skip this:

.. code-block:: vim

let g:jedi#auto_vim_configuration = 0

You can make jedi-vim use tabs when going to a definition etc:

.. code-block:: vim

let g:jedi#use_tabs_not_buffers = 1

If you are a person who likes to use VIM-splits, you might want to put this in your


.. code-block:: vim

let g:jedi#use_splits_not_buffers = "left"

This options could be "left", "right", "top", "bottom" or "winwidth". It will decide the direction where the split open.

Jedi automatically starts the completion, if you type a dot, e.g.

, if you don't want this:

.. code-block:: vim

let g:jedi#popup_on_dot = 0

Jedi selects the first line of the completion menu: for a better typing-flow and usually saves one keypress.

.. code-block:: vim

let g:jedi#popup_select_first = 0

Jedi displays function call signatures in insert mode in real-time, highlighting the current argument. The call signatures can be displayed as a pop-up in the buffer (set to 1 by default (with the conceal feature), 2 otherwise), which has the advantage of being easier to refer to (but is a hack with many drawbacks since it changes the buffer's contents), or in Vim's command line aligned with the function call (set to 2), which can improve the integrity of Vim's undo history.

.. code-block:: vim

let g:jedi#show_call_signatures = "1"

Here are a few more defaults for actions, read the docs (

:help jedi-vim
) to get more information. If you set them to
, they are not assigned.

.. code-block:: vim

NOTE: subject to change!

let g:jedi#goto_command = "d" let g:jedi#goto_assignments_command = "g" let g:jedi#goto_stubs_command = "s" let g:jedi#goto_definitions_command = "" let g:jedi#documentation_command = "K" let g:jedi#usages_command = "n" let g:jedi#completions_command = "" let g:jedi#rename_command = "r"

Finally, if you don't want completion, but all the other features, use:

.. code-block:: vim

let g:jedi#completions_enabled = 0


I don't want the docstring window to popup during completion

This depends on the

option. Jedi initializes it in its
. Add the following line to your
to disable it:

.. code-block:: vim

autocmd FileType python setlocal completeopt-=preview

I want to do autocompletion

Don't even think about changing the Jedi command to


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

   let g:pymode_rope = 0

See issue

  1. You can also use
    __ 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


jedi-vim is being tested with a combination of

_ and

The tests are in the

subdirectory, you can run them calling::

The tests are automatically run with


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.