Feature Request: Automatic Environment Activation in Terminal

[DonJayamanne]

From @threecgreen on August 4, 2017 15:57

Current behavior

Every time I open the built-in terminal in VSCode, I have to remember to activate the project's Python environment.

Expected behavior

I'd like $ source activate my_env for conda or $ source bin/activate for virtualenv to run at VSCode terminal startup if I have selected an Python interpreter other than the system default.

Copied from original issue: DonJayamanne/pythonVSCode#1139

[DonJayamanne]

From @smcstewart on August 22, 2017 9:37

So, if you have a local .vscode/settings.json with the python.venvPath set, then the terminal could automatically source it. I'd +1 that.

[DonJayamanne]

You can use the command, 'Python REPL'.
Unfortunately there is no easy to change the external terminal.

[DonJayamanne]

From @meichthys on September 11, 2017 13:28

@smcstewart were you referring to an external terminal or the integrated vscode terminal?

[DonJayamanne]

From @smcstewart on September 11, 2017 14:44

@MatthewGieger Yeah, the integrated vscode terminal. The external terminal makes no sense and I can manage that myself. However, if I'm inside an existing Python project, when I open the integrated terminal, it'd be great to automatically source the virtualenv. I thought this was what @threecgreen was getting at.

[DonJayamanne]

From @meichthys on September 11, 2017 14:49

@smcstewart Yes, agreed. I think that was indeed what @threecgreen was getting at.

@DonJayamanne Do you know if this has been implemented in any way? Also, what do you mean about using the "Python REPL" command? Could you give a quick example?

[DonJayamanne]

From @fourierserious on December 9, 2017 22:10

In User/Workspace Settings, I use

"terminal.integrated.shellArgs.linux": [
    "--rcfile", "/home/jacob/miniconda3/envs/vscode/etc/bash.bashrc"
]

with the following in my bash.bashrc

source /home/jacob/.bashrc
source /home/jacob/miniconda3/bin/activate vscode

[DonJayamanne]

@brettcannon
Considering the fact that we need to activate the conda environment for conda installs #561,
do we want to extend this feature to the following areas as well:

• Executing python files in the terminal (we have a command for this)
• Executing python scripts (code) in the terminal (we have a command or this too)
• Launching the REPL

Makes sense (less code = easier) to implement this as a generic feature across the board when sending anything to a terminal from our code.
However this would be a change in current behavior. I don't see how this could be a problem though.

[brettcannon]

I say "yes". Basically when it comes to conda, we should run through an activated environment when possible.

[brettcannon]

And if people complain we will point out that Anaconda said we should do it this way. 😁