You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attempting to install an anaconda package from within vscode fails. Executing the same command from the anaconda shell works.
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS Z:\myproj> Z:/Miniconda3/Scripts/activate
PS Z:\myproj> conda activate myenviron
conda : The term 'conda' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included,
verify that the path is correct and try again.
At line:1 char:1
+ conda activate myenviron
+ ~~~~~
+ CategoryInfo : ObjectNotFound: (conda:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS Z:\myproj> & Z:/Miniconda3/Scripts/conda.exe install --name myenviron rope
Collecting package metadata: failed
CondaHTTPError: HTTP 000 CONNECTION FAILED for url <https://repo.anaconda.com/pkgs/main/noarch/repodata.json.bz2>
Elapsed: -
An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.
If your current network has https://www.anaconda.com blocked, please file
a support request with your network engineering team.
SSLError(MaxRetryError('HTTPSConnectionPool(host=\'repo.anaconda.com\', port=443): Max retries exceeded with url: /pkgs/main/noarch/repodata.json.bz2 (Caused by SSLError("Can\'t connect to HTTPS URL because the SSL module is not available."))'))
PS Z:\myproj>
Extension version: 2019.4.12954
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17763
System Info
Item
Value
CPUs
Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz (4 x 2295)
When the Anaconda / Miniconda python distribution is installed with an installer of the current version on Windows, the conda is no longer added to the PATH environment variable.
Yes, however we expect users to setup their powershell environment for conda to start working.
The latest version of conda has instructions on how to do this, i believe the command is conda init.
Closing as we expect users to setup their shells for conda to work.
The extension will no longer attempt to resolve this on behalf of the user.
Issue Type: Bug
Possibly related to #5503.
Attempting to install an anaconda package from within vscode fails. Executing the same command from the anaconda shell works.
Extension version: 2019.4.12954
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17763
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: