With g:jedi#popup_on_dot = 1, jedi-vim starts completion after typing three consecutive dots (i.e. ..., the Ellipsis object). This is rather disorientating, and causes issues when trying to write a function stub (e.g. in a .pyi file for type hinting), as pressing enter will insert the first completion (which happens to be abs, as Jedi decides to complete globals).

Note that ... is a valid Python 3 expression, but is not valid Python 2 syntax.

Running latest jedi-vim HEAD (which is, as at time of writing, commit dc23f0b), using Python 3.

Of course, let g:jedi#popup_on_dot = 0 is a workaround, but it's a sucky workaround 😄