Skip to content

Conversation

@eleanorjboyd
Copy link
Member

@eleanorjboyd eleanorjboyd commented Jun 23, 2025

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.

@vs-code-engineering
Copy link

⚠️ This PR originates from a fork. Due to security restrictions, pipelines from forks are no longer triggered automatically. Learn more.

If the changes appear safe, you can manually trigger the pipeline by commenting /AzurePipelines run.

@vs-code-engineering vs-code-engineering bot added this to the June 2025 milestone Jun 23, 2025
@eleanorjboyd eleanorjboyd added skip package*.json package.json and package-lock.json don't both need updating skip-issue-check debt Covers everything internal: CI, testing, refactoring of the codebase, etc. labels Jun 23, 2025
@eleanorjboyd eleanorjboyd requested review from cwebster-99 and karthiknadig and removed request for karthiknadig June 23, 2025 18:21
Tyriar
Tyriar previously approved these changes Jun 23, 2025
@vs-code-engineering
Copy link

⚠️ This PR originates from a fork. Due to security restrictions, pipelines from forks are no longer triggered automatically. Learn more.

If the changes appear safe, you can manually trigger the pipeline by commenting /AzurePipelines run.

@eleanorjboyd eleanorjboyd merged commit df13df0 into microsoft:main Jun 23, 2025
46 checks passed
@eleanorjboyd eleanorjboyd deleted the cognitive-termite branch June 23, 2025 20:11
@kinto0
Copy link

kinto0 commented Jun 23, 2025

hi @eleanorjboyd, is the plan to deprecate all of these APIs related to obtaining environments in favor of the environments extension? or is it expected that extensions should still depend on ms-python.python?

@eleanorjboyd
Copy link
Member Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

debt Covers everything internal: CI, testing, refactoring of the codebase, etc. skip package*.json package.json and package-lock.json don't both need updating skip-issue-check

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants