pylsp-rope VS pyright

pylsp-rope is actually an external plugin project, it implements advanced refactoring functionalities using code action (extract method/variable, function inlining, converting local variables to instance variables, organise import, etc). Unless you have explicitly installed pylsp-rope at some point, it's unlikely you already have it in your system. I'm the author of pylsp-rope, btw.

If you're also a user of rope, which is a Python refactoring library, my python-lsp-server plugin pylsp-rope would also welcome contributions. They have a fairly small codebase, and so they would be relatively easy to pick up.

Currently the best way to use rope for refactoring (including extract, inlining, reorganise import, plus many more) in Neovim is with pylsp-rope and your preferred LSP client. pylsp-rope is going to be the main focus of bringing rope capabilities to various IDEs and text editors. I'll have to find the time for this, but I'm planning to overhaul the rope support in core pylsp to make it work even better.

Rope's Restructuring refactoring is very powerful and flexible, and it's very accurate given the pattern, however it's currently only accessible from rope's programmatic interface, which means you have to write a little bit of Python code to use it. I've not been able to figure out how best to expose this capability into easy to use user interface within text editors/IDEs and especially within the constraints of LSP for pylsp-rope.

I am the maintainer rope and pylsp-rope. They are libraries for automated Python refactoring and to do that from any LSP-capable editors. We are always welcoming contributors of all levels.

You can also use pylsp-rope, though until LSP actually provides a standard Villani compliant interface that allows LS to implement move refactoring, you may not be able to use it from your editor. I'm kinda thinking that maybe I should just non-standard LSP extension that ropevim would call into. It shouldn't just be Microsoft that can play EEE 😅

pylsp-rope

I never had to market an open source project from zero that later grow into popularity, but I did inherit the maintainership of a fairly popular project and then I started a new project that have been gaining a small, but growing momentum.

Most of my personal projects are written because I need a feature that nobody else has anything remotely resembling what I need.

pylsp-rope for refactoring capabilities

Pyright is a fast type checker meant for large Python source bases. It can run in a “watch” mode and performs fast incremental updates when files are modified.

However, I made it faster for my use-case by changing some settings. Neovim allows to have these settings in the setup function for LSP. I was trying to figure out how do I change these settings with doom emacs. Pyright docs suggest to have these settings in pyrightconfig.json.

Not exactly what you are looking for but maybe useful to others.

https://github.com/microsoft/pyright/blob/main/docs/mypy-com...

You can use pyright instead[0]. It is the FOSS version of pyright, but having some features missing.

[0]: https://github.com/microsoft/pyright

Unfortunately, pyright explicitly stated that they are not interested in inlay hints or other language server features, that those will only be added to pylance. That's why I added it myself instead of submitting a pull request to pyright. See https://github.com/microsoft/pyright/issues/4325

return { -- add pyright to lspconfig { "neovim/nvim-lspconfig", ---@class PluginLspOpts opts = { ---@type lspconfig.options servers = { -- Listed servers will be automatically loaded to buffers jsonls = { settings = { json = { format = { enable = true, }, }, validate = { enable = true }, }, }, pyright = { settings = { python = { analysis = { -- https://github.com/microsoft/pyright/blob/main/docs/settings.md autoSearchPaths = false, useLibraryCodeForTypes = true, diagnosticMode = "openFilesOnly", }, }, }, }, }, -- Add folding capability to use LSP for ufo plugin capabilities = { textDocument = { foldingRange = { dynamicRegistration = false, lineFoldingOnly = true, }, }, }, }, }, }

[{ "resource": "/Documents/Coding/VSCode/Projects/Photoeditor/PhotoEditor.py", "owner": "_generated_diagnostic_collection_name_#0", "code": { "value": "reportMissingModuleSource", "target": { "$mid": 1, "external": "https://github.com/microsoft/pyright/blob/main/docs/configuration.md#reportMissingModuleSource", "path": "/microsoft/pyright/blob/main/docs/configuration.md", "scheme": "https", "authority": "github.com", "fragment": "reportMissingModuleSource" } }, "severity": 4, "message": "Import \"requests\" could not be resolved from source", "source": "Pylance", "startLineNumber": 2, "startColumn": 8, "endLineNumber": 2, "endColumn": 16 }]

I don't use astro, but you can configure pyright by using a pyrightconfig.json or directly in the LSP configuration.

I prefer jedi over pyright as pyright has crippled documentation support outside of VSCode. I also found jedi is make correct suggestions based on inferred type in some situations where pyright would need type annotation to provide completions, pyright is significantly faster though. Jedi with mypy and flake8 is comparable to pyright I think, but unfortunately mypy wasn't working over tramp. Also isort wasn't working over tramp, but jedi, black, importmagic and flake8 all worked.