- Notifications
You must be signed in to change notification settings - Fork1.2k
add python.useEnvironmentsExtension#25204
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
If the changes appear safe, you can manually trigger the pipeline by commenting |
2d0c635 tofb35750CompareIf the changes appear safe, you can manually trigger the pipeline by commenting |
df13df0 intomicrosoft:mainUh oh!
There was an error while loading.Please reload this page.
kinto0 commentedJun 23, 2025
hi@eleanorjboyd, is the plan to deprecate all ofthese APIs related to obtaining environments in favor of the environments extension? or is it expected that extensions should still depend on ms-python.python? |
Hello@kinto0 we will keep the exiting APIs until we can get the envs extension to stable. After that we will mark them for deprecation, and over time deprecate them. No change should be made now from extensions and we will provide ample warning for the deprecation and switch. Hopefully this helps- thanks so much! |
Uh oh!
There was an error while loading.Please reload this page.
step 1 of insiders envs ext rollout. In the activation function, set
python.config.useEnvironmentsExtension:true(so for everyone with envs extension installed). Result: all users with extension envs extension installed (and using it while we have this bake) will get this in their user settings and thus when experimentation starts they will override any control/treatment group.