-
Notifications
You must be signed in to change notification settings - Fork 113
vscode-python upstream merge v2025.12.0 #9162
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
base: main
Are you sure you want to change the base?
Conversation
packageJson.extensionPack = ['ms-python.debugpy'].concat( | ||
packageJson.extensionPack = [ | ||
// --- Start Positron --- | ||
//'ms-python.vscode-pylance', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
adjusting this slightly so we know what extension dependencies we are not using. ms-python.vscode-python-envs
is now a bundled/required dependency.
@@ -681,6 +686,16 @@ | |||
"scope": "resource", | |||
"type": "string" | |||
}, | |||
"python.useEnvironmentsExtension": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we want to expose this, even though we do not bundle the environments extension?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think let's hide this setting. It's definitely causing enough confusion upstream and IMO it would be even more confusing here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed setting!
Release Notes
New Features
vscode-python
release,v2025.12.0
.Bug Fixes
QA Notes
green ci, everything acting normally