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

[DonJayamanne]

Problems

• Open a folder in a terminal and create a pip env
• Next open VSC and open a completely different folder
• VSC will not identify the above pipenv as a virtual env

Cause:

• Extension has discovered all interpreters and above pipenv is not detected as a pipenv (unfortunately its treated as a virtual env, pipenv doesn't provide an api to get around this).
• Now above env is treated as virtual env
• Next when we open the folder which has the pipenv mapped to it, the pipenv will not get activated correctly.