PipClientHandler: hand over to UvHandler when uv is available

[aveao]

Recent PRs to this project introduced a UvHandler and UvVenvManager, which provide very helpful functionality.

I can understand why you might not want to change over all users of PipClientHandler and PipVenvManager to use them (though I think it's worth consideration), but I believe it would be an improvement if PipClientHandler were expanded with functionality to hand over to UvHandler if there's uv installed on the system and the current project utilizes it.

This way, the versions of packages within the uv venv can be utilized, which is useful in cases where a project depends on a different version of the LSP than what is installed system-wide.

(Adjacent issue on LSP-ruff to not force a specific version so that the local project's version can be used where possible: sublimelsp/LSP-ruff#131)

[rchl]

I'm planning to migrate to UvVenvManager but I don't think that would solve your issues.

UV in that case would be used to install a managed ruff instance in ST's Package Storage without affecting system or current project in any way.

[aveao]

Ah yeah, I see now that UvVenvManager uses the path of the package storage as its workdir. Should've poked around more before opening the issues, sorry.

Does it sound good if I close this and the feature request on lsp-ruff, and instead open another feature request on this repo to use the version of the package within the project's own uv venv if it contains the required package?

I would be happy to contribute a PR to LSP-ruff to use UvRunner, btw.

[rchl]

I've created PR to use Uv for LSP-ruff - sublimelsp/LSP-ruff#132

As for using workspace ruff, this was discussed in length in various places. I think the least effort option is to just let user override command if he chooses to use non-managed ruff. Then we take no responsibility if the version is not compatible with package settings.

As for something more complex that detects venv (and ruff within it) I'm not sure about but feel free to create issue for it.

LSP-pyright includes code for detecting vens. Perhaps it could be shared in some way but not convinced yet that we should add all that complexity.