How to handle "ModuleNotFoundError: No module named 'pylsp.plugins.rope_rename'" #588
Comments
|
I encountered this |
|
I'm having the same issue with neovim after a recent update of packages and lsp servers on my system. Could this be related to #515? |
|
Here is a traceback that might help magically, just adding an empty |
|
Adding the file works for me. Thanks @dcherian! |
|
The issue seems to have been resolved. I updated yesterday, without manually adding any files, and I no longer see the error. |
|
Strange, I still see the error if I remove the What did you update? I've got all the latest updates for packages installed via Lazy and I use Mason for my LSP servers and that is still showing 1.12.0 for python-lsp-server with no available updates. |
I stand corrected... after updating this morning, I now see the crash again, but it was definitely not broken when I posted last time. Someone seems to keep messing up and there's no official response in this thread, either... BTW, if anyone's wondering where, exactly, you should |
|
Just posting here to bump it, because it started happening again last Friday and is still present today, as of this writing. The same solution still applies, though. Maybe it's time that the plugin import is at last placed within a |
|
This is still happening, any news? |
All I can say is that I've not run into the problem again since the last time I manually applied the fix(es) described above. |
|
I haven't run into this problem on linux with the newest version, but on windows I had a case where I, accidentally, had installed the server via winget and via pip at the same time and this error popped up. After removing the winget installation, it vanished. |
|
I just fix this error by uninstalling an old version python-lsp-server in user path $ pip list | grep python
python-lsp-jsonrpc 1.0.0
python-lsp-server 1.7.1
$ pip uninstall python-lsp-serverand I reproduce this error by installing old version python-lsp-server and restart neovim my mason pylsp venv package version Hopefully, my approach can be helpful. |
Hello,
I was updating all my Emacs (29 from Debian 12 backports) packages after a while and no got this error. After doing some research it seems that rope-support was removed from pylsp.
I installed it explicit via
pip install -U pylsp-ropebut nothing changed.OK, I am also fine with just disabling rope in my setup. But I don't know how. I don't see "rope" in my init.el.
My (reduced) init.el is ~240 lines long. Not sure if it make sense to post it here.
Any suggestion how to go further with analyzing this?
The text was updated successfully, but these errors were encountered: