deoplete-jedi processes are running even if I edit non-py file about deoplete-jedi HOT 7 CLOSED

FWIW: I've tried to get remote_pdb into this, but failed: https://github.com/ionelmc/python-remote-pdb.

It would be nice to trigger this through SIGUSR to see what is going on.

from deoplete-jedi.

I have tested it. But I cannot reproduce it with your minimal init.vim and reproduce ways.
deoplete-jedi processes are generated after editing Python script.

from deoplete-jedi.

@Shougo
Are you sure? (were you tricked by let g:deoplete#enable_at_startup = 1 not being run directly)

set rtp+=~/.vim/neobundles/deoplete
set rtp+=~/.vim/neobundles/deoplete-jedi
let g:deoplete#enable_at_startup = 1

Run :exe '!pstree -apl' getpid():

nvim,27759 -u vimrc.minimal
  |-pstree,27849 -apl 27759
  |-python3,27795 -c import sys; sys.path.remove(""); import neovim; neovim.start_host() /home/user/.vim/neobundles/deoplete/rplugin/python3/deoplete
  |   `-python,27831 -u /home/user/.vim/neobundles/deoplete-jedi/rplugin/python3/deoplete/sources/deoplete_jedi/server.py --desc-length 0 --debug
  `-{nvim},27832

I've looked into this / Shougo/deoplete.nvim#336, and not starting deoplete-jedi always would be very nice to have in general already.
(this can be done by lazy-loading through the plugin manager probably, but should not be necessary?!)

from deoplete-jedi.

@rafi reproduced. re-opened.
Sorry.

from deoplete-jedi.

@rafi @blueyed It's a bug.
But @Shougo said will fix on deoplete.nvim sources side.
Please wait for the update of deoplete.nvim.

@Shougo Thanks for follow up.

from deoplete-jedi.

@zchee @Shougo I have updated the minimal init.vim to reproduce in the description above.

from deoplete-jedi.

It is fixed in the latest deoplete.

from deoplete-jedi.