-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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 |
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-rope
but 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: