Compiling and running as ruff server

[rlovell3]

This recent ruff-lsp issue has thrown me a curve ball, and I'm now faced with cleaning up a (my own) mess. Let me start by saying I spend most of my time in Rust rather than Python, but really appreciate how ruff watches my back when I'm doing the snake.

This is a system config question. I currently have ruff installed in a conda environment, but I'm about to remove it. What I PREFER is to git clone ..., compile, symlink the binaries to a place in my path, and live happily ever after. I don't want to use the astral installer script. I haven't looked at it yet, but if it requires sudo, I'm, already not interested. I like my machine and its years of configuration to remain exactly as I've painstakingly crafted it, including locations of 3rd party repos that I happily compile/make/build/whatever locally.

Back to my config idea. I've now done the above: git cloned, compiled, symlinked, this ruff GitHub repo, and it runs beautifully. The question is, do I need to set this up as a server with a service, or just call it when I need it? Also, given my preferred "build local" setup, do I need to inform the VS Code plugin of my {localized, non-conda, non-pip, non ev} binary and its related mountain of target/release/{*.rlib, *.so} libs?

Amazing work guys and gals. Professional in all regards.

[MichaReiser]

You can use the ruff.path setting to tell the extension to use your ruff binary. The extension otherwise uses the pre-built binary that ships with the extension itself.

You don't have to run ruff server as a server. The extension calls ruff server internally