Don't use activate from inside conda environments

[xhochy]

In contrast to virtualenv-created environments, conda environments are not activated from the inside. In constrast, the environment activation is done from the outside via the conda executable that created the environment.

Fixes #4402

• Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
• Title summarizes what is changing
• Has a news entry file (remember to thank yourself!)
• Appropriate comments and documentation strings in the code
• Has sufficient logging.
• Has telemetry for enhancements.
• Unit tests & system/integration tests are added/updated
• Test plan is updated as appropriate
• package-lock.json has been regenerated by running npm install (if dependencies have changed)
• The wiki is updated with any design decisions/details.

[xhochy]

To test this, one simply can create a conda environment where the conda package itself is installed. As I'm new to contributing to VSCode extensions, I would need some guidance how I write a test for this.

[xhochy]

@rchiodo This should be the most non-invasive version to load the environment correctly and fix #4402

[rchiodo]

Yeah this seems right to me too. You look in the base environment first.

---

In reply to: 489090205 [](ancestors = 489090205)

[rchiodo]

The unit tests we already have should be verifying the interpreter path for the existing cases.

Other than that, we'd like to test it on Mac/Linux/Windows with conda and non conda environments.

---

In reply to: 487750270 [](ancestors = 487750270)

[rchiodo]

I can try on windows.

---

In reply to: 489131081 [](ancestors = 489131081,487750270)

[rchiodo]

Works good on windows.

---

In reply to: 489131165 [](ancestors = 489131165,489131081,487750270)

[rchiodo]

[aldanor]

Could a patch version be released with this please? It's a pretty big change if it makes conda environments usable again.

Edit: no, it still doesn't work :( (#5539)