Open Pipenv terminal with pipenv shell

[iddan]

Environment data

• VS Code version: 1.28.0
• Extension version (available under the Extensions sidebar): 2018.9.0
• OS and version: macOS Mojave 10.14
• Python version (& distribution if applicable, e.g. Anaconda): 3.6.5
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pipenv

Actual behavior

When pipenv venv detected terminal is opened by:

source $VENV_LOCATION/bin/activate

Expected behavior

Terminal to open with:

pipenv shell

Why?

Because that way .env would be loaded automatically and activating shell would be encapsulated

[wcass77]

Is it possible to turn off automatic activation of the virtual environment, or at least get a new shell where it isn't active? For whatever reason this feature wasn't working for me until today (not sure why), but now it is and I would like to turn it off. I sometimes run other things from the terminal in vscode, and I usually use pipenv run with custom aliases in the Pipfile to run things anyway.

Alternatively, the shell could launch a regular shell session and then issue the command pipenv shell as suggested above. That way ctrl-d would exit the virtual environment and drop you into a regular shell. Currently ctrl-d closes the shell completely.

I'm running 1.28.0 and 2018.9.0 of the plugin. I'm running the dev version of pipenv (installed from the master branch on github 2 days ago), as there are bugs in the currently released version. I'm running python 3.7 installed via pyenv.

[DonJayamanne]

Willy Cass (@wcass77)
To disable activation of the terminal, please update your settings as follows:
"python.terminal.activateEnvironment": false