You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 31, 2023. It is now read-only.
It would be nice if the lsp-python-ms-python-executable-cmd setting could be scoped to single server instances (workspaces) somehow. If you edit multiple projects in the same instance of Emacs, and some of them are Python2 while others are Python3 (or using different venvs), then there should be a way to assign the correct python version for each.
Scoping the setting to the workspace level makes the most sense to me, since buffers can also be part of multiple workspaces (?) so a buffer-local variable is not a great fit. Also many buffers can be part of a single workspace, so they must share the same python version (which also makes this a bad fit for a buffer local variable).
The text was updated successfully, but these errors were encountered:
It would be nice if the
lsp-python-ms-python-executable-cmd
setting could be scoped to single server instances (workspaces) somehow. If you edit multiple projects in the same instance of Emacs, and some of them are Python2 while others are Python3 (or using different venvs), then there should be a way to assign the correct python version for each.Scoping the setting to the workspace level makes the most sense to me, since buffers can also be part of multiple workspaces (?) so a buffer-local variable is not a great fit. Also many buffers can be part of a single workspace, so they must share the same python version (which also makes this a bad fit for a buffer local variable).
The text was updated successfully, but these errors were encountered: