You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
New workspace virtual environments are not discovered until VS Code reloads #656
We are going to scope this to just virtual environments created in the workspace folder (should take into consideration the fact that pipenv can create its virtual environment locally when a certain environment variable is set).
changed the title [-]New virtual environments are not discovered until VS Code resets[/-][+]New workspace virtual environments are not discovered until VS Code reloads[/+]on Sep 20, 2018
Activity
brettcannon commentedon Sep 20, 2018
We are going to scope this to just virtual environments created in the workspace folder (should take into consideration the fact that pipenv can create its virtual environment locally when a certain environment variable is set).
[-]New virtual environments are not discovered until VS Code resets[/-][+]New workspace virtual environments are not discovered until VS Code reloads[/+]DonJayamanne commentedon Sep 20, 2018
Solution:
Use lookForInterpretersInDirectory
Progress indicator when loading interpreters and speed up detection o…
brettcannon commentedon Nov 5, 2018
This doesn't seem to re-trigger if a virtual environment is deleted. Is that expected?