Virtualenvs not displaying in interpreter selector

[bjlange]

Environment data

• VS Code version: 1.23.1
• Extension version (available under the Extensions sidebar): 2018.4.0
• OS and version: macOS Sierra, 10.12.6 (16G1314)
• Python version (& distribution if applicable, e.g. Anaconda): 3.6.1 (installed via pyenv)
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
• Relevant/affected Python packages and their versions: N/A

Actual behavior

No virtualenv interpreters show up in the interpreter selector.

Expected behavior

My virtualenv interpreters would be selectable in the interpreter selector.

Steps to reproduce:

1. Open the command palette
2. Select Python: Select Interpreter
3. Only my pyenv interpreters and system interpreters are displayed (no virtualenvs)

I'll note that this used to work fine. I installed pyenv recently to manage python versions on my machine.. I'm not certain that this problem began immediately after I did that, but that might have been the cause.

Logs

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

nothing related to this problem (just pylint outputs for the file I have open)

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

[Extension Host] Python Extension (lookForInterpretersInVenvs): TypeError: Cannot read property 'on' of undefined
	at on (/Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/common/process/proc.js:93:15)
	at ProcessService.exec (/Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/common/process/proc.js:104:9)
	at InterpreterVersionService.<anonymous> (/Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/interpreter/interpreterVersion.js:30:40)
	at Generator.next (<anonymous>)
	at /Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/interpreter/interpreterVersion.js:16:71
	at Promise (<anonymous>)
	at __awaiter (/Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/interpreter/interpreterVersion.js:12:12)
	at InterpreterVersionService.getVersion (/Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/interpreter/interpreterVersion.js:29:16)
	at WorkspaceVirtualEnvService.<anonymous> (/Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/interpreter/locators/services/baseVirtualEnvService.js:83:38)
	at Generator.next (<anonymous>)
	at /Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/interpreter/locators/services/baseVirtualEnvService.js:16:71
	at Promise (<anonymous>)
	at __awaiter (/Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/interpreter/locators/services/baseVirtualEnvService.js:12:12)
	at WorkspaceVirtualEnvService.getVirtualEnvDetails (/Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/interpreter/locators/services/baseVirtualEnvService.js:81:16)
	at Promise.all.interpreters.map.interpreter (/Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/interpreter/locators/services/baseVirtualEnvService.js:55:88)
	at Array.map (native)
	at fileSystem.getSubDirectoriesAsync.then.then.then.then.then.interpreters (/Users/brian/.vscode/extensions/ms-python.python-2018.4.0/out/client/interpreter/locators/services/baseVirtualEnvService.js:55:64)
	at <anonymous>
t.log @ console.ts:136

followed by this, for each of my virtualenvs:

 ERR spawn /Users/brian/.virtualenvs/teamster/bin/python2.7 EAGAIN: Error: spawn /Users/brian/.virtualenvs/teamster/bin/python2.7 EAGAIN
	at exports._errnoException (util.js:1050:11)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
	at onErrorNT (internal/child_process.js:367:16)
	at _combinedTickCallback (internal/process/next_tick.js:80:11)
	at process._tickCallback (internal/process/next_tick.js:104:9)

[brettcannon]

Where do the virtual environments exist relative to your workspace folder and/or home directory?

[bjlange]

They exist in ~/.virtualenvs/. The workspace folder is at ~/projects/project-name. I tried setting my users settings for python.venvPath to ~/.virtualenvs but that hasn't helped.

[brettcannon]

@bjlange to help us debug this faster, could you try it with a trailing whitespace and then try it with an absolute path (independently to help figure out if either of these things is the problem)? If you can't get to it we understand as we will eventually get around to testing this ourselves.

[bjlange]

Sure. Tested a number of options:

• ~/.virtualenvs: same Cannot read property 'on' of undefined error documented above
• ~/.virtualenvs (trailing space): no error this time, but still the venvs don't show up
• ~/.virtualenvs/ (trailing slash): same Cannot read property 'on' of undefined error
• /Users/brian/.virtualenvs(absolute path): same Cannot read property 'on' of undefined error
• /Users/brian/.virtualenvs/(absolute path, trailing space): no error this time, but still the venvs don't show up
• /Users/brian/.virtualenvs/(absolute path, trailing slash): same Cannot read property 'on' of undefined error

[brettcannon]

@bjlange thanks for that! Last thing, could you past in your setttings.json?

[bjlange]

Here it is. I made sure I'm in a workspace that has no workspace-specific settings too.

// Place your settings in this file to overwrite the default settings
{
    // Controls the font family.
    "editor.fontFamily": "'Input Mono Condensed', Menlo, Monaco, 'Courier New', monospace",
    // Controls the font size in pixels.
    "editor.fontSize": 13,
    // Columns at which to show vertical rulers
    "editor.rulers": [
        80
    ],

    // 4 spaces but follow what's there
    "editor.insertSpaces": true,
    "editor.tabSize": 4,
    "editor.detectIndentation": true,

    // Customizes which terminal application to run on OS X.
    "terminal.external.osxExec": "iTerm.app",
    "files.exclude": {
        "**/.git": true,
        "**/.svn": true,
        "**/.hg": true,
        "**/.DS_Store": true,
        "**/*.pyc": true,
        "**/.ipynb_checkpoints": true,
        "**/.idea": true,
        "**/.cache": true
    },
    "window.zoomLevel": 0,
    "git.confirmSync": false,
    "editor.wordWrap": "on",
    "workbench.iconTheme": "vs-seti",
    // Port number to use for connection.
    "remote.port": 52698,

    // Launch the server on start up.
    "remote.onstartup": true,

    // only at top of doc
    "gitlens.codeLens.enabled": false,

    "editor.renderWhitespace": "boundary",
    "editor.renderControlCharacters": true,
    "workbench.colorCustomizations": {
        "editorWhitespace.foreground": "#292929"
    },
    "workbench.editor.tabSizing": "shrink",
    "explorer.confirmDragAndDrop": false,
    "gitlens.advanced.messages": {
        "suppressCommitHasNoPreviousCommitWarning": false,
        "suppressCommitNotFoundWarning": false,
        "suppressFileNotUnderSourceControlWarning": false,
        "suppressGitVersionWarning": false,
        "suppressLineUncommittedWarning": false,
        "suppressNoRepositoryWarning": false,
        "suppressResultsExplorerNotice": false,
        "suppressShowKeyBindingsNotice": true,
        "suppressUpdateNotice": false,
        "suppressWelcomeNotice": true
    },
    "git.autofetch": true,
    "gitlens.keymap": "alternate",
    "python.venvPath": "~/.virtualenvs"
}

[brettcannon]

I can't reproduce on Windows 10, so I'll flag this as a macOS thing and see if someone on that platform can reproduce.

[DonJayamanne]

@bjlange

• Please could you install our latest development build from here and let us know whether you are still able to replicate this issue.