Issue with Select Interpreter / Create Terminal after creation of new virtualenv

[david-waterworth]

Steps to cause the bug to occur

1. Create a new pyenv-virtualenv in the vscode terminal pyenv virtualenv 3.7.6 my-virtual-env- 3.7.6
2. F1 Python: Select Interpreter and choose the newly created my-virtual-env- 3.7.6
3. F1 Python: Create Terminal (or start a Jupyter notebook)

Actual behavior

Starts the wrong interpreter

Expected behavior

Start the right interpreter

It seems to be caching the interpret list and not being aware it's been changed from underneath. Restarting vscode fixes the issue

[ericsnowcurrently]

@david-waterworth, thanks for letting us know about this. We will work on fixing the issue as soon as we can.

[david-waterworth]

It also doesn't seem to be 100% deterministic. Today I created a new pyenv-virtualenv from the vscode terminal. It didn't show up at all in the list of interpreters until I restarted vscode. Then it appeared but the first time I tried to enable an error was raised. Then it worked

Command 'Python: Select Interpreter' resulted in an error (command 'python.setInterpreter' not found)

[karrtikr]

Fixed in latest release of extension.