Closed QingShuiHU closed 4 weeks ago
Hi, it looks like you're using Python 3.8.13 ('sensity':conda) environment. Note that the IPython
extension doesn't activate the environment, it's the MS Python
extension that does that. Maybe that extension and/or vscode behaviors had change in newer version.
What is the vscode version you're using?
Thank you for your reply. I am using vscode version 1.91.1. Note that I used vscode for remote development.It is true that the selected conda environment is not automatically activated in the remote terminal(The operating system of the server is Ubuntu). Locally and not remotely, vscode can automatically activate the environment (by using Command Prompt) How can I solve this problem, thank you
Locally and not remotely, vscode can automatically activate the environment (by using Command Prompt) How can I solve this problem, thank you
Are you using WSL to connect with the remote terminal? Also, is the environment 'sensitive:conda' the remote environment?
Typically, if the proper environment is selected, VSCode should be able to activate the terminal correctly. So when you startup your remote terminal, check if the environment the remote terminal have access to vs. the environment current selected at the bottom right are the same.
It appears that the issue is resolved.
ipython cannot automatically activate the conda environment on the vscode remote terminal, and ipython reports an error: The remote terminal does not automatically activate the conda environment