Ignore pipenv when python.pythonPath is already set

[juanchristian]

Environment data

• VS Code version: 1.23.0
• Extension version (available under the Extensions sidebar): 2018.4.0
• OS and version: Windows 10 Enterprise 2016 LTSB 10.0.14393.0
• Python version (& distribution if applicable, e.g. Anaconda): Python x64 3.6.5
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pipenv
• Relevant/affected Python packages and their versions: pipenv 11.10.0

Actual behavior

When I open my project folder I get the following error:

Expected behavior

I should get no error. My .vscode/settings.json is properly configured. This same project folder was working a week ago, but now when I open it I get the error cited above.

Workspace settings

{
    "python.pythonPath": "C:\\Users\\<username>\\.virtualenvs\\amazing-project-xyz12Abc\\scripts\\python.exe"
}

Steps to reproduce:

1. Open a project folder configured to use pipenv

Logs

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

##########Linting Output - pylint##########
No config file found, using default configuration

--------------------------------------------------------------------

Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00)

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

console.ts:136 [Extension Host] vscode-icons is active!
console.ts:136 [Extension Host] Error: No virtualenv has been created for this project yet!
	at PipEnvService.<anonymous> (C:\Users\<username>\.vscode\extensions\ms-python.python-2018.4.0\out\client\interpreter\locators\services\pipEnvService.js:113:31)
	at Generator.next (<anonymous>)
	at fulfilled (C:\Users\<username>\.vscode\extensions\ms-python.python-2018.4.0\out\client\interpreter\locators\services\pipEnvService.js:15:58)
	at <anonymous>
t.log @ console.ts:136

[DonJayamanne]

Please could you type the following in your terminal window and let me know what you get:
pipenv --venv

[maximegregoire]

I get the same message on Mac OS. pipenv --venv gives me the correct location of my virtual environment (/Users/<my_username>/.local/share/virtualenvs/<my_folder_name>-50WkzGzt)

[brettcannon]

@maximegregoire what happens if you unset python.pythonPath in your settings? And what if you have pipenv recreate the virtual environment?

Basically the solution for us would be for us to ignore pipenv if you set python.pythonPath.

[maximegregoire]

@brettcannon Unsetting the pythonPath setting did the trick! Thanks!

[juanchristian]

@DonJayamanne Sorry for the late reply. I get the following:

PS C:\Users\...\amazing-project> pipenv --venv
No virtualenv has been created for this project yet!

I tried removing python.pythonPath but it didn't work, as I got the same error.