pylsp-rope VS LSP

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

I saw no mention of RBS+Steep, the latter providing a LSP. I use it a lot and very much like it, although it's still young and needs love, but it's making good, steady progress! I've been very pleasantly surprised by some of the crazy things Steep can catch, completely statically!

You appear to be working on projects with Sorbet (which I tried to like but found it fell short in practice, notably outside of the app use case i.e it's mostly useless for gems) so it may be a tall order to try on those. Maybe you can give RBS+Steep a shot on some small project?

RBS: https://github.com/ruby/rbs

RBS collection (for those gems that don't ship RBS signatures in `sig`, integrates with bundler): https://github.com/ruby/gem_rbs_collection

Steep: https://github.com/soutaro/steep

VS Code: https://github.com/soutaro/steep-vscode

Sublime Text: https://github.com/sublimelsp/LSP

Vim (I'm working on it): https://github.com/dense-analysis/ale/pull/4671

Psalm - support for Psalm can be added via the LSP plugin. More information about it can be found in Psalm's documentation.

You obviously never tried the various LSP plugins for ST. It will give you the same intelllgent code tools as the jetbrains IDEs, which goes way beyond just syntax highlighting and linting and there's support for a lot of languages. https://lsp.sublimetext.io/

Add in this and you're golden: https://github.com/sublimelsp/LSP

https://github.com/sublimelsp/LSP with https://github.com/sublimelsp/LSP-typescript works pretty well for me. They are also both being actively maintained. It'd be nice if it was built-in, but it works well enough that I still have not found a compelling reason to switch to VSCode.

I really love sublime and it doesn't seem to be dead just yet. Sublime Text 4 was also a pretty great release.

I tried sublime this year now that it has an LSP (language server), along with the Go plugin. Maybe it would take more getting used to, but VSCode has done such a great job for coding in. Sublime's project view just wasn't as good either.

I really still like sublime for editing text or log files on my dev system, but not for development.

https://github.com/sublimelsp/LSP

not a fan of that but there is https://github.com/sublimelsp/LSP/pull/1702

That's great, try it with SublimeLSP and gopls.