Support "pipx run" command as lsp-bridge-python-command #1101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
In recent years, it has become very difficult to do a system-wide pip install as described in the README due to PEP 668 – Marking Python base environments as “externally managed”.
Solution
pipx run
transparently creates a virtual environment and automatically resolves the latest dependencies.pipx
supports PEP 723 – Inline script metadata, so packages embedded inlsp_bridge.py
scripts will be automatically installed.The tradeoff is that we have to wait a few seconds on startup for the dependency checks, which was not a pain for me since it only happens when the server starts.
To enable
pipx
to start servers, just set the following option:(setopt lsp-bridge-python-command "pipx")
What do you think about offering an opt-in feature like this?