Whenever elpy-mode
is activated upon visiting a python file, I see a py.exe
executable start, with a subtree of processes. This should be the remote procedure call (thanks @al0 for the explanation). It's what Elpy uses to check syntax, documentation, etc. Just to be clear I'm not speaking of the Python interpreter, started with run-python
.
After I kill the buffer with the python code and elpy-mode
, I see that the spanned RPC process and its tree are still alive. This happens even if I don't have any buffers, open or buried, with elpy-mode
.
I don't quite see the point of the RPC remaining alive. Is this by design? Is there a command or function to kill it? At the moment I must open the task manager to kill it.
elpy-rpc-restart
kills the rpc, and it restarts it – but only if the elpy buffer still exists. So a solution is to first kill the buffer and then callM-x elpy-rpc-restart
. Maybe this can be automated in some hook. Please feel free to write your suggestion as a solution.M-x list-processes
elpy-rpc
. Killing that buffer also kills the process. Thank you very much.