Skip to content

feat: manage the server with UV#206

Merged
rchl merged 3 commits intomasterfrom
fix/use-uv
Feb 27, 2026
Merged

feat: manage the server with UV#206
rchl merged 3 commits intomasterfrom
fix/use-uv

Conversation

@rchl
Copy link
Copy Markdown
Member

@rchl rchl commented Feb 26, 2026

Switch from using PIP to UV.

UV can satisfy Python version requirement automatically if existing one doesn't match or it's not present at all.

Fixes #204
Fixes #125

Comment on lines -25 to -29
// Defines the Python interpreter to use for creating an environment in which `pylsp` server will run.
// The value can be set to a binary name (like `python`, in which case a binary with that name needs to be present
// on the PATH) or a full path to the Python interpreter binary.
// When the value is `null` then it defaults to `python` on Windows and `python3` on other platforms.
"python_binary": null,
Copy link
Copy Markdown
Member Author

@rchl rchl Feb 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, perhaps this should still be supported but since UV is good at finding system python and falls back to downloading I'm not sure it makes sense...

It was to fix #102 but now, with pyproject.toml specifying required python version, it won't be an issue as long as we make sure that the requirement is up to date.

@rchl rchl merged commit 8836e53 into master Feb 27, 2026
1 of 2 checks passed
@rchl rchl deleted the fix/use-uv branch February 27, 2026 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

pylsp-mypy==0.7.1 incompatible with sublime python Unalbe to start subprocess for LSP-pylsp

1 participant