Repository navigation
Conda Issues #5344
Description
Activity
- added this to the 2019, week 15 - April Sprint 8 milestone
on Apr 17, 2019 - locked and limited conversation to collaborators
on Apr 17, 2019 Suggestions/Notes:
- A/B test the changes
- Upstream VS Code fix (Support using a "clean" environment for the terminal vscode#70248)
- Required
-
No support for conda version < 4.6
Leave as is for now. Current approach is a best approach. - Minimum version of Conda Supported is 4.6
- Suggest YES
- Should we expect users to have their shells pre-configured for Conda
- I.e. ensure conda is in their path, etc...
- Currently we attempt to get around this by running some conda scripts prior to activation of an environment.
- Suggest YES for Non-Windows
- Activation on Windows
- Activate base environment (this is required to ensure we first setup
conda) - Then activate the required environment
- Activate base environment (this is required to ensure we first setup
- Enable activating conda environments by path
- Its possible to create conda environments in a specific folder, in this case we need to activate it using the path not the name.
- Suggest YES (enhancement)
Conda notes on activation:
-
conda create
Create a new conda environment from a list of specified packages. To use the created environment, use 'source activate envname' look in that directory first. This command requires either the -n NAME or -p PREFIX option. -
conda activate $ENVNAME
Instructions can be found here (applies to >= 4.6) -
activation & paths
Conda commands used to switch or move between installed environments. The conda activate command prepends the path of your current environment to the PATH environment variable so that you do not need to type it each time. deactivate removes it. Even when an environment is deactivated, you can still execute programs in that environment by specifying their paths directly, as in ~/anaconda/envs/envname/bin/program_name. When an environment is activated, you can execute the program in that environment with just program_name. -
Conda will never work in VSC
- See here for details
- Ensure ~/.bash_profile is clean
- Install ananconda
- Activation scripts will be added into
~/.bash_profile- However this is conditional
- Hacky solution - Set path for anaconda when ever a terminal is opened.
- Currently the path is set conditionally, we could probably prepend the path always. (I.e. rather than getting conda to add the path conditionally, we can do it ALWAYS)
- modified the milestones: 2019, week 15 - April Sprint 8, 2019, week 17 - April Sprint 9
on Apr 24, 2019 TODO
** Conda Requirements**
- Look at comments in Conda command broken for new anaconda python installations #5503 (comment)
- File issues on Conda GitHub repo
- Idempotency of conda startup scripts in
./bash_profile& other platforms - Add support for conda startup scripts in Command Prompt and PS
- What are the commands for Command Prompt?
- What are the commands for PowerShell?
- Note: We will expect users to have configured powershell for Conda.
- If we have them, where are they?
- Else current solution is
actiavte base env, thenactivate specific env
53 remaining items
Closing as stale.
Use
conda infoconda infowork on a vanilla install of Conda Spike - Can we useconda listandconda infoall the info we need to work with conda #6882Use
conda activateconda activateto activate conda environments (i.e. no more calls tosource) Spike - Use only conda activate, stop calling source #8864Use
conda runPythonExecutionFactoryandPythonExecutionServicefix the following (Update PythonExecutionService to support "conda run". #7696):exec()(Stop using "exec()" in the extension. #7697):installers (partial): In one case we usesudoand inpoetrycase we use path to binary directly. So this could not be addressed directly.debugger (partial): python debug adapter uses adapter descriptor. So no changes were madeinterpreter discovery (partial): Discussed with Don and should not be switched to python execution factory.PythonExecutionFactoryfor running pythonpipenv shell#4203 )Verifying conda work is done
Basically we are no longer doing any shenanigans behind conda's back to support it and we are using the provided tooling as expected.
condacommand to get the list of environmentsconda activateto activate environments (i.e. don't usesource)conda run