-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Activating Conda environment fails #2315
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
I'm unable to replicate this at my end, must be cuz I have conda installed. |
I think #1882 might have the solution. I.e. using |
Time to use the linux environment. |
This issue might have a dependency on #2266 (see #2266 (comment)) |
Lets leave this open, this issue is similar to #1882, but we need to ensure this is also resolved (i.e. ensure we install Anaconda via pipenv) |
Closing in favour of #1882 |
Python: Create Terminal
command activates the(root)
conda enviornment in VSCode instead of the configured environment.Environment data
Workspace Settings
Actual behavior
The
(root)
environment is activated for a folder instead of the configured/specified one.Expected behavior
The specified/configured environment is activated.
Steps to reproduce:
> pyenv install anaconda3-4.4.0
/home/user/conda_issue
.> conda create -n conda_issue python=3.6.1
(note Python version is same as what is associated with anaconda3-4.4.0)
> echo "print('hello world')" > hello_world.py
Python 3.6.1 :: Anaconda 4.4.0 (64-bit) (anaconda3-4.4.0)
one.Python: Create Terminal
.Logs
Output sent to the interactive terminal:
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)N/A (nothing output)
Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
)N/A (nothing output)
The text was updated successfully, but these errors were encountered: