Vscode-remote-release: cannot select python interpreter from my venv on WSL

[uishon]

• VSCode Version:
• Local OS Version: Windows 10. 1809.
• Remote OS Version: WSL (Ubuntu 18.10)
• Remote Extension/Connection Type: WSL

Steps to Reproduce:

1. set python.venvPath in python extension setting to ~/.virtualenvs (on remote, not user)
2. try select interpreter from the command palette (or simply click on the interpreter listed on the status bar) - VS code shows a list of interpreters to choose from but not the ones under ~/.virtualenvs.

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: Yes/No

[ricjuanflores]

Add to wsl settings:

"python.pythonPath": "~/.virtualenvs/venv_test/bin/python",

[uishon]

It works. Thanks.

On Fri, May 3, 2019 at 11:44 PM Juan Ricardo Flores <
[email protected]> wrote:

Add to wsl settings:

"python.pythonPath": "~/.virtualenvs/venv_test/bin/python",

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-remote-release/issues/70#issuecomment-489233894,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACMZVKPMS55LSUN72Z4PN3DPTSP25ANCNFSM4HKTZ4OQ
.

[uishon]

Hmm... Just tried the same with remote-ssh but here it didn't work :-(
I was able to select one of my virtualenvs by changing this
"python.pythonPath" to that specific virtualenv and that worked but it
still doesn't list the other virtualenvs to select from.

On Sat, May 4, 2019 at 9:59 PM Uri Ishon [e-mail] wrote:

It works. Thanks.

On Fri, May 3, 2019 at 11:44 PM Juan Ricardo Flores <
[email protected]> wrote:

Add to wsl settings:

"python.pythonPath": "~/.virtualenvs/venv_test/bin/python",

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-remote-release/issues/70#issuecomment-489233894,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACMZVKPMS55LSUN72Z4PN3DPTSP25ANCNFSM4HKTZ4OQ
.

[uishon]

Just a quick update.
When I opened a new remote-ssh window - all virtualenvs are listed properly.
That original remote-ssh window which remained open, however, is still not
showing them all.

On Sat, May 4, 2019 at 10:29 PM Uri Ishon [e-mail] wrote:

Hmm... Just tried the same with remote-ssh but here it didn't work :-(
I was able to select one of my virtualenvs by changing this
"python.pythonPath" to that specific virtualenv and that worked but it
still doesn't list the other virtualenvs to select from.

On Sat, May 4, 2019 at 9:59 PM Uri Ishon [e-mail] wrote:

It works. Thanks.

On Fri, May 3, 2019 at 11:44 PM Juan Ricardo Flores <
[email protected]> wrote:

Add to wsl settings:

"python.pythonPath": "~/.virtualenvs/venv_test/bin/python",

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode-remote-release/issues/70#issuecomment-489233894,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACMZVKPMS55LSUN72Z4PN3DPTSP25ANCNFSM4HKTZ4OQ
.

[egamma]

FYI @qubitron

[qubitron]

@DonJayamanne @BrettCannon can you comment on whether the venvPath setting is expected to work here?

[DonJayamanne]

@uishon

• When adding "python.venvPath": "~/.virtualenvs" do you not see the environments in WSL or SSH or both?
• Are there any errors logged in the Console Window accessible from Help-> Toggle Developer Tools menu.

That original remote-ssh window which remained open, however, is still not
showing them all.

Is this still the case?

[uishon]

Sorry it took me some time to respond...

Anyway, now I see the virtual environments in both WSL and SSH.
That already opened ssh-window is closed by now so I can't really reply to
your question but at least as long as I kept it open, it never showed up
the virtualenvs list correctly. Only new windows did.

Uri.

On Thu, May 9, 2019 at 9:36 PM Don Jayamanne [e-mail]
wrote:

@uishon https://github.com/uishon

• When adding "python.venvPath": "~/.virtualenvs" do you not see the
  environments in WSL or SSH or both?
• Are there any errors logged in the Console Window accessible from Help->
  Toggle Developer Tools menu.

That original remote-ssh window which remained open, however, is still not
showing them all.

Is this still the case?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-remote-release/issues/70#issuecomment-491018290,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACMZVKKOEMCVJUV7Y3UV63LPURVL7ANCNFSM4HKTZ4OQ
.

[DonJayamanne]

@uishon Thanks for getting back to us.
Its most likely the discovery of interpreters was taking a little longer than usual. The way it works is we discover interpreters in the background.

@kieferrm I believe we can consider this issue resolved.

[phtn]

install Remote - WSL extension.

[sleighsoft]

Not for WSL but I cannot change my environment on a linux server I am connected to. It properly lists all available conda environments but when selecting one (either from bottom menu / or by "select interpreter") nothing changes.

[brettcannon]

@sleighsoft are you saying that your Linux server isn't running under WSL?

[sleighsoft]

Yes, it is an ubuntu server. Not WSL.
And when I login with vscode remote I always defaults to the same conda environment and I cannot choose another one. There is also nothing in any of the remote logs indicating what does or does not happen when I try to change the interpreter.

Edit:
It has now, for whatever reason, unselected the current interpreter and I can no longer choose a new one and therefore not use the debugger :/

Edit 2:
Completely removing the vscode installation on the remote and then reconnecting so that vscode reinstalls itself solved that issue. Seems like one of the previous vscode updates broke it.
Maybe in addition to Kill Server on remote something like Reinstall server on remote would be nice :)

[fangaofeng]

i open folder with wsl，then File->Preferences-> settings->Remote [WSL:Ubuntu] change my setting, not effect. it effect by local settings.
When i change .vscode/settings.json is same as Remote[WSL:Ubuntu].json, python can run. But it change local file .This Remote settings:

{
    "python.venvPath": "/home/fgf",
    "python.venvFolders": [
        "whlenv"
    ],
    "python.pythonPath": "/home/fgf/whlenv/bin/python",
    //"python.pipenvPath": "E:\\pythonvenv\\trainserver-PFVxFgBL\\Scripts\\pipenv.exe",
    //"python.pipenvPath": "C:\\Python\\Python37\\Scripts\\pipenv.exe",
    "python.terminal.activateEnvironment": true,
    "python.autoComplete.addBrackets": false,
    // "python.linting.flake8Enabled": true,
    "python.linting.pycodestyleEnabled": true,
    "python.formatting.provider": "autopep8",
    "python.formatting.autopep8Args": [
        "--max-line-length",
        "120",
        "--experimental"
    ],
    // "python.sortImports.args": ["-rc", "--atomic"],
    // "python.formatting.yapfArgs": ["--style", "{based_on_style:pep8}"],
    "editor.formatOnSave": true,
    "editor.tabCompletion": "on",
    "python.analysis.logLevel": "Trace",
    "python.analysis.diagnosticPublishDelay": 1000,
    "python.analysis.openFilesOnly": false,
    "python.analysis.symbolsHierarchyDepthLimit": 20,
    //"svn.path": "c:\\Program Files\\TortoiseSVN\\bin",
    "git.ignoreLimitWarning": true,
    "python.autoComplete.extraPaths": [
        "/home/fgf/whlenv/Lib/site-packages"
    ],
    "python.linting.pylintEnabled": false,
    "python.linting.maxNumberOfProblems": 120,
    "files.associations": {
        "**/templates/*.html": "django-html",
        "**/templates/*": "django-txt",
        "**/requirements{/**,*}.{txt,in}": "pip-requirements"
    },
    "emmet.includeLanguages": {
        "django-html": "html"
    }
}

[raeperd]

1. Ctrl + Shift + p
2. python: Select Interpreter
3. Choose virtual environment

This was my solution

[bamurtaugh]

Reviewing this thread - it looks like we can consider the original issue resolved? If folks aren't still experiencing it, I'll go ahead and close it.

[bamurtaugh]

Closing based on above comment - thanks all!