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