Skip to content

Activating a conda environment using conda instead of source #1882

@eyadsibai

Description

@eyadsibai

Environment data

  • VS Code version: 1.23.1
  • Extension version (available under the Extensions sidebar): 2018.5.0
  • OS and version: Linux Manjaro 4.16.13-1
  • Python version (& distribution if applicable, e.g. Anaconda): 3.6.3 / conda version: 4.5.2
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda

Actual behavior

I am using the zsh shell. When I create a new python terminal it uses source activate 'name_of_environment'

Expected behavior

I am using the zsh shell. When I create a new python terminal it uses conda activate 'name_of_environment

Steps to reproduce:

  1. install latest conda
  2. add ". /etc/profile.d/conda.sh" to your .zshrc file as recommended by any conda version after 4.4
  3. try to create a new python terminal within vscode whille the activateEnviroment setting is true

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-terminalbugIssue identified by VS Code Team member as probable bugimportantIssue identified as high-prioritylinuxmacos

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions