- pylsp-rope version: 0.1.16
- Text editor/IDE/LSP Client: Emacs (IDE), Eglot (LSP client)
- Python version: 3.12.6
- Operating System: MacOS
Description
I just had couple of questions w.r.t. the renaming functionality.
-
The README states that pylsp.plugins.pylsp_rope.rename should be configured to enable rename support. However, it is unclear to me how it should be configured. E.g. is pylsp.plugins.pylsp_rope.rename a boolean config or something else? Or should I use pylsp.plugins.pylsp_rope.rename.enabled?
-
Once I have set it the above config correctly, how do I know my LSP's rename function calls pylsp-rope's rename function instead of the default one.
-
From the README it looks like renaming has only been implemented for variables, classes and functions. To my knowledge, python-lsp-servers native rename functionality already covers this. Would you say that currently pylsp-ropes rename feature does not provide any additional benefit, until the modules and packages renaming have also been implemented?
Thanks and I already really love pylsp-rope as it is!
Description
I just had couple of questions w.r.t. the renaming functionality.
The README states that
pylsp.plugins.pylsp_rope.renameshould be configured to enable rename support. However, it is unclear to me how it should be configured. E.g. ispylsp.plugins.pylsp_rope.renamea boolean config or something else? Or should I usepylsp.plugins.pylsp_rope.rename.enabled?Once I have set it the above config correctly, how do I know my LSP's rename function calls pylsp-rope's rename function instead of the default one.
From the README it looks like renaming has only been implemented for variables, classes and functions. To my knowledge,
python-lsp-servers native rename functionality already covers this. Would you say that currentlypylsp-ropes rename feature does not provide any additional benefit, until the modules and packages renaming have also been implemented?Thanks and I already really love
pylsp-ropeas it is!