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
I have a system wide conda install (/usr/bin/conda). While vscode detects all my conda environments correctly, it fails to activate them correctly, leading to various things not working, like test discovery, starting a jupyter server, etc.
My understanding is conda calls source activate <env> or equivalent to activate and environment. There is no activate script in my path, so this fails. I have tried setting python.condaPath to /usr/bin/conda, but all it does is call source /usr/bin/activate <env> instead; again that fails.
I found an old issue (#1882) that points to something like my problem, but I couldn't quite find a resolution. If there was an easy way to configure what command is used to activate an environment, that would be great. Maybe a list of command templates that can be tried in order until one succeeds, ["conda activate <env>", "source activate <env>", "workon <env>", ...] and so on.
Extension version: 2019.10.38574-dev
VS Code version: Code - Insiders 1.39.0-insider (e0762af, 2019-09-27T05:26:55.061Z)
OS version: Linux x64 5.1.20-300.fc30.x86_64
Remote OS version: Linux x64 5.2.14-200.fc30.x86_64
System Info
Item
Value
CPUs
AMD Ryzen 5 2400G with Radeon Vega Graphics (8 x 1811)
You don't need to have it, we search for the activate script using path to conda interpreter. Anyways, we are moving to using conda run which runs an executable from within a conda environment without activating it. It won't need activate, so this would be fixing all these issues. Closing this in favor of #7425 .
Issue Type: Bug
I have a system wide conda install (
/usr/bin/conda
). While vscode detects all my conda environments correctly, it fails to activate them correctly, leading to various things not working, like test discovery, starting a jupyter server, etc.My understanding is conda calls
source activate <env>
or equivalent to activate and environment. There is noactivate
script in my path, so this fails. I have tried settingpython.condaPath
to/usr/bin/conda
, but all it does is callsource /usr/bin/activate <env>
instead; again that fails.I found an old issue (#1882) that points to something like my problem, but I couldn't quite find a resolution. If there was an easy way to configure what command is used to activate an environment, that would be great. Maybe a list of command templates that can be tried in order until one succeeds,
["conda activate <env>", "source activate <env>", "workon <env>", ...]
and so on.Extension version: 2019.10.38574-dev
VS Code version: Code - Insiders 1.39.0-insider (e0762af, 2019-09-27T05:26:55.061Z)
OS version: Linux x64 5.1.20-300.fc30.x86_64
Remote OS version: Linux x64 5.2.14-200.fc30.x86_64
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: disabled_software
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: unavailable_off
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: