Solution to issue cannot be found in the documentation.
[X] I checked the documentation.
Issue
This is on Apple Silicon M1 and miniforge3 conda version 23.3.1. Upgrading to this version has caused an issue with VSCode's default python interpreter, where instead of using conda activate on initializing a new shell, it will run source activate instead.
source activate /Users/aaronteo/Documents/.. ../.venv
source: no such file or directory: activate
Now I had only done the upgrade recently, so I decide to check my base environment revision history and revert to its last good working state.
Solution to issue cannot be found in the documentation.
Issue
This is on Apple Silicon M1 and miniforge3 conda version 23.3.1. Upgrading to this version has caused an issue with VSCode's default python interpreter, where instead of using
conda activate
on initializing a new shell, it will runsource activate
instead.Now I had only done the upgrade recently, so I decide to check my
base
environment revision history and revert to its last good working state.I then tried to revert back to revision 2.
Following this down-revision to conda version 22.11.1, the VSCode default python interpreter now works as intended. Very strange!
Installed packages
Environment info