Rope VS vim-jumpsuite

Hi, maintainer of rope here. There are a number of different options to use rope in Vim/Neovim, we've documented them in this page https://github.com/python-rope/rope/wiki/Rope-in-Vim-or-Neovim

If you're looking for something with a bigger codebase, then the rope library in which pylsp-rope is based on is also welcoming of contributions.

I think rope is the standard for refactoring, and should provide autoimports soon, though pyright might also be good for that.

rope

If you are interested in discussing this or have ideas you want to sketch out, meet me at rope's GitHub Discussion.

However, my biggest and most popular open source project is one that I don't originally write, but rather I inherited a popular project that has been abandoned by their original author/maintainers. I use Python a lot, so I wanted to contribute to the community in a significant way, so unlike my other projects I do take the time promoting this project as well. I felt it's more like a community service for this project.

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.

Rope has first class support for Vim and it can do a move refactoring, among other refactorings. From this, this feature is available from python-mode and ropevim.

rope

Okay this depends: if your code is static: perfectly possible for example with https://github.com/python-rope/rope (used for example by VS Code). If it's dynamic / generated via metaprogramming: I never tried it but I can't imagine that it'd work there, yes. However java tooling also can't do that because it simply doesn't support metaprogramming in any noteworthy way.

Oh, you're in luck because I've actually written this exact plugin, it's called vim-jumpsuite. It is personally one of my special weapons that's becoming completely indispensable for me.

vim-jumpsuite: parses python tracebacks and identifies the most "interesting" part of the stack to create a jump list; despite vim being in the name, the python part of the plug-in is usable with any editors that supports parsing grep/quickfix-style output

Here is link number 1 - Previous text "my"

vim-jumpsuite for creating a quickfix/loclist jumps out of unittest tracebacks

vim-test with lieryan/vim-jumpsuite

For more elaborate cases, I wrote a plugin that summarises python traceback into the quickfix list. vim-jumpsuite is designed to be used when writing unittest/pytest; for each failing test, it'll try to pick the three most important locations that you'll want to jump to. You can also configure certain files/functions to never be picked by vim-jumpsuite.

Plug: one of the most valuable plugin for me are the vim plugin that I wrote myself: lieryan/vim-jumpsuite. It's a plugin to quickly jump to "interesting" line of code from your test suite by converting unittest reports to a Quickfix jumplist. The plugin uses some customizable heuristics to find the lines from tracebacks that are most likely to be most useful to your code.