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 great if there were a variable that can be overridden to either pass the complete path to a virtualenv directory, or a pattern used to discover virtualenvs. As it is right now there is a hardcoded set of options for locating the python executable for a given buffer, but it is rigid and doesn't match everyone's preferred means of organizing their Venvs.
It would also be great if it could automatically use the $WORKON_HOME value that gets set by tools such as virtualenvwrapper or pyvenv.
In conjunction with this, it would be helpful to add some documentation to specify how the python interpreter is selected and any ways that get added to configure that.
The text was updated successfully, but these errors were encountered:
It's not clear to me. Which part is hardcoded? Do you mean lsp-python-ms-locate-python? I think the PR is better since I am not using virtualenvs locally.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be great if there were a variable that can be overridden to either pass the complete path to a virtualenv directory, or a pattern used to discover virtualenvs. As it is right now there is a hardcoded set of options for locating the python executable for a given buffer, but it is rigid and doesn't match everyone's preferred means of organizing their Venvs.
It would also be great if it could automatically use the
$WORKON_HOME
value that gets set by tools such as virtualenvwrapper or pyvenv.In conjunction with this, it would be helpful to add some documentation to specify how the python interpreter is selected and any ways that get added to configure that.
The text was updated successfully, but these errors were encountered: