Can't autodetect pipenv on 2018.2.1

[frostming]

Environment data

• VS Code version: 1.21.0: 2018 Feb
• Extension version (available under the Extensions sidebar): 2018.2.1
• OS and version: macOs High Sierra 10.13.3
• Python version: CPython 3.6.4
• Type of virtual environment used (if applicable): pipenv
• Relevant/affected Python packages and their versions: pipenv==11.3.2

Actual behavior

When open a project with Pipfile, the interpreter is bare Python 3.6.4

Expected behavior

When open a project with Pipfile, the interpreter will be autodetected as Python3.6.4(pipenv) and uses the virtualenv created by pipenv

Steps to reproduce:

1. pipenv install to create a virtualenv for requests_html
2. Open the project in VSCode

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Only linting messages

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

[Extension Host] (node:33660) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
t.log @ workbench.main.js:sourcemap:257

[DonJayamanne]

I've tested this at my end and it seems to work.
Please could you provide the following info:

• Do you have a .vscode folder created (it should get created automatically)
• What are the contents of the .vscode/settings.json file?
• When in the requests_html directory please type the following in the terminal window and let me know what you get:
  pipenv --venv

[frostming]

I deleted .vscode folder and restarted. Since I haven't changed interpreter manually, the folder didn't create again.

The other question:

> pipenv --venv
/Users/fming/.local/share/virtualenvs/requests-html--yMYlALf

[DonJayamanne]

deleted .vscode folder and restarted.

What was in the folder?
How did it get created in the first place?

[DonJayamanne]

Once in vscode please remember to create/open a python file, this will activate the python extension.

[frostming]

Yes, I opened a py file.

The first time I chose the python interpreter so it was written in settings.

[brettcannon]

Two things:

1. Can you update your version of pipenv? (latest version is 11.6.0)
2. Where is your Pipfile in your workspace? (E.g. is it at the root folder?)

[brettcannon]

And thanks for helping us with this! 😃

[brettcannon]

And as a third thing, can you do this before you upgrade?

pipenv --venv
echo $?

Basically we would like to know if the pipenv --venv command had a non-zero exit code.