Ask questionsCreating a new terminal does not automatically activate the chosen conda interpreter

<!-- Please search existing issues to avoid creating duplicates. -->

Environment data

  • VS Code version: Version: 1.46.1 Commit: cd9ea6488829f560dc949a8b2fb789f3cdc05f5d Date: 2020-06-17T21:17:14.222Z Electron: 7.3.1 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: OS: Darwin x64 18.7.0

  • Extension version (available under the Extensions sidebar): XXX

  • OS and version: MacOS Mojave

  • Python version (& distribution if applicable, e.g. Anaconda): conda 4.8.3 python 3.7

  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda

  • Relevant/affected Python packages and their versions: XXX

  • Relevant/affected Python-related VS Code extensions and their versions: XXX

  • Value of the python.languageServer setting: XXX

Expected behaviour

My understanding is that when creating a new terminal it should automatically load the chosen interpreter

Actual behaviour

It starts terminal with base conda environment.

Steps to reproduce:

Not sure what's relevant here. But I installed conda, setup an env in an outside terminal. Then restarted VSCode and chose the correct interpreter. But terminals still open with base conda env


Answer questions karrtikr

Hi @rahul003 , I would need additional info for this. Please provide the logs as mentioned in the issue template, and also, the extension version.



<summary>Output for <code>Python</code> in the <code>Output</code> panel (<code>View</code>→<code>Output</code>, change the drop-down the upper-right of the <code>Output</code> panel to <code>Python</code>) </summary>



</p> </details>

<br />


<summary> Output from <code>Console</code> under the <code>Developer Tools</code> panel (toggle Developer Tools on under <code>Help</code>; turn on source maps to make any tracebacks be useful by running <code>Enable source map support for extension debugging</code>) </summary>



</p> </details>

Does having this in user setting work?

  "python.experiments.optOutFrom": ["DeprecatePythonPath - experiment"]

Related questions

Auto Scroll in the Jupyter output hot 3
Workspace contains pipfile but pipenv --venv failed hot 2
Can you turn off the Microsoft Python Language Server? hot 2
Unable to debug Python tests (duplicate entries in &#34;env&#34;) hot 2
Jupyter server crashed. Unable to connect. Cannot assign requested address hot 2
Auto Scroll in the Jupyter output hot 2
Unable to run launch targets with newest VS Code Python extension hot 2
Unable to start jupyter python interactive window hot 1
HBox output is not shown correctly in the interactive window hot 1
Debug -> Add Debug Configuration 'Cannot read property openConfigFile' hot 1
VSCode cannot connect to jupyter server; with browser this works fine hot 1
Linux arm64/aarch64 support hot 1
Add setting to disable icon for "Run Python File In Terminal" hot 1
Extension Host keeps crashing hot 1
Activate environment before debugging tests hot 1
Github User Rank List