Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode extension does not notify server when python interpreter is changed #703

Closed
alcarney opened this issue Dec 29, 2023 · 0 comments · Fixed by #750
Closed

VSCode extension does not notify server when python interpreter is changed #703

alcarney opened this issue Dec 29, 2023 · 0 comments · Fixed by #750
Labels
bug Something isn't working ide:vscode Issues that relate to the Esbonio vscode extension
Milestone

Comments

@alcarney
Copy link
Member

While the VSCode extension sends a workspace/didChangeConfiguration message when the user changes esbonio.* options, no such message is sent when the user chooses a new Python interpreter to use in a given workspace.

This means the server will carry on using whichever python interpreter was configured first and not be able to react to the change.

@alcarney alcarney added bug Something isn't working ide:vscode Issues that relate to the Esbonio vscode extension labels Dec 29, 2023
@alcarney alcarney added this to the 1.0 milestone Dec 29, 2023
@alcarney alcarney added this to Esbonio Dec 29, 2023
@github-project-automation github-project-automation bot moved this to Todo in Esbonio Dec 29, 2023
@github-project-automation github-project-automation bot moved this from Todo to Done in Esbonio Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ide:vscode Issues that relate to the Esbonio vscode extension
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant