Exposed API updateActiveEnvironmentPath outside workspace #25045
Labels
feature-request
Request for new features or functionality
triage-needed
Needs assignment to the proper sub-team
Comments
|
@Ma-Shell That API will eventually be replaced by APIs from https://github.com/microsoft/vscode-python-environments extension. That extension supports setting Python for PEP-723 style scripts out of the box. Not only for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The public API of vscode-python exposes the function
environments.updateActiveEnvironmentPath.This function only works, when operating within a workspace. If I open VSCode with just a single Python file and try to execute this function, the output-log shows:
[error] Cannot update workspace settings as no workspace is openedHowever, switching over the builtin-menu in the status bar is possible, even when not in a workspace.
Background info and reproducible example:
I wrote an extension related to this feature request: #24916.
As suggested in #21783, my extension https://github.com/Ma-Shell/uvscode uses the exposed updateActiveEnvironmentPath-function to automatically switch the interpreter for PEP 723 compatible scripts based on the currently edited file to the result of
uv python find --script. This works, when opening a folder but not when opening individual files without a workspace.The extension is currently not on the extensions marketplace and needs to be compiled manually to use. The error message stated above is not displayed in the debugger but within the instance that has the extension loaded, when selecting "Python" in the Output console.
The text was updated successfully, but these errors were encountered: