-
Notifications
You must be signed in to change notification settings - Fork 1.2k
conda environment fails to load properly on remote machine #11324
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
Comments
@RMeli Did this ever work in any particular version of the extension? |
@karthiknadig Unfortunately I'm not sure, since I use VSCode Remote sporadically... Something I forgot to mention is that I'm using Miniconda instead of Anaconda on both machines. Could that be a problem? |
@DonJayamanne I need your opinion on this. @RMeli seems to be having this issue since before I think this is an issue with VSCode terminal or |
Closing as stale. |
Environment data
"python.jediEnabled"
set to; more info How to update the language server to the latest stable version #3977): False (Local) / True (Remote/Workspace)python.languageServer
setting: MicrosoftExpected behaviour
I expect
conda
environment to work on remote machines. I still get the issue described in #6896 (which is now locked and I can't comment anymore).Actual behaviour
When I open a new Terminal on a remote machine, after selecting the Python environment in VSCode, I get the following:
I checked I have the following line in my settings for both the local machine (
User
), the remote machine (Remore [SSH: YYY]
) and the workspace (Workspace
):According to Launch terminals with clean environments
$SHLVL
variable should be1
, but this is not the case:Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)The text was updated successfully, but these errors were encountered: