Skip to content

Conda command broken for new anaconda python installations #5503

@ARF1

Description

@ARF1

Issue Type: Bug

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.

See: https://docs.anaconda.com/anaconda/reference/release-notes/#what-s-new-in-anaconda-4-4

The python extension however still calls the command conda (and presumably others) as if they were available in PATH.

PS Z:\testfolder> conda activate myenv
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 myenv
+ ~~~~~
    + CategoryInfo          : ObjectNotFound: (conda:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Steps to reproduce:

  1. Run without debug any python file with an anaconda environment selected.

Extension version: 2019.4.11987
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)
GPU Status 2d_canvas: enabled
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
Memory (System) 7.88GB (3.18GB free)
Process Argv Z:\testfolder
Screen Reader no
VM 0%

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions