-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot select python interpreter from my venv on WSL #70
Comments
Add to wsl settings:
|
It works. Thanks.
…On Fri, May 3, 2019 at 11:44 PM Juan Ricardo Flores < ***@***.***> 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
<#70 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACMZVKPMS55LSUN72Z4PN3DPTSP25ANCNFSM4HKTZ4OQ>
.
|
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 ***@***.***> wrote:
It works. Thanks.
On Fri, May 3, 2019 at 11:44 PM Juan Ricardo Flores <
***@***.***> 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
> <#70 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACMZVKPMS55LSUN72Z4PN3DPTSP25ANCNFSM4HKTZ4OQ>
> .
>
|
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 ***@***.***> 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 ***@***.***> wrote:
> It works. Thanks.
>
> On Fri, May 3, 2019 at 11:44 PM Juan Ricardo Flores <
> ***@***.***> 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
>> <#70 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/ACMZVKPMS55LSUN72Z4PN3DPTSP25ANCNFSM4HKTZ4OQ>
>> .
>>
>
|
FYI @qubitron |
@DonJayamanne @brettcannon can you comment on whether the venvPath setting is expected to work here? |
Is this still the case? |
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 ***@***.***> 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
<#70 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACMZVKKOEMCVJUV7Y3UV63LPURVL7ANCNFSM4HKTZ4OQ>
.
|
install |
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. |
@sleighsoft are you saying that your Linux server isn't running under WSL? |
Yes, it is an ubuntu server. Not WSL. Edit: Edit 2: |
i open folder with wsl,then File->Preferences-> settings->Remote [WSL:Ubuntu] change my setting, not effect. it effect by local settings.
|
This was my solution |
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. |
Closing based on above comment - thanks all! |
Steps to Reproduce:
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
The text was updated successfully, but these errors were encountered: