User Tools

Site Tools


other:uvcdat:cdat_conda:miniconda3_install

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
other:uvcdat:cdat_conda:miniconda3_install [2025/08/22 17:24] – [Useful conda commands] Started experimenting with export/create jypeterother:uvcdat:cdat_conda:miniconda3_install [2025/09/17 14:24] (current) – [Useful conda commands] More export details jypeter
Line 622: Line 622:
   * **Available environments**   * **Available environments**
     * ''conda env list''     * ''conda env list''
-      * Same as ''conda info --envs''+      * Same as ''conda info %%--%%envs''
     * The currently active environment has a "*****" character on its line<code>(base) $ conda env list     * The currently active environment has a "*****" character on its line<code>(base) $ conda env list
 # conda environments: # conda environments:
Line 715: Line 715:
  
   * **Export the description of an environment** (as a checkpoint, or to replicate the environment somewhere else)   * **Export the description of an environment** (as a checkpoint, or to replicate the environment somewhere else)
-    * Example: ''conda export -n bauer_env --format yml --from-history -f ./bauer_env_2025-08-22.yml''+    * There are lots of [[https://docs.conda.io/projects/conda/en/stable/commands/export.html#|export options]] available, but we recommend the following combination of options. 
 +      * The options used below will create a text file ([[https://en.wikipedia.org/wiki/YAML|YAML]] format) listing the names of the Python packages that were installed with ''conda install -n existing_environment_name package_name''. This file does not specify the packages' version and their dependencies and can be used later to easily reproduce an environment (using the latest available version of the requested packages) 
 +      * ''conda export -n existing_environment_name %%--%%format yml %%--%%from-history -f some_path/existing_environment_yyyy-mm-dd.yml'' 
 +        * Windows example:\\ ''conda export -n base %%--%%format yml %%--%%from-history -f C:\Users\your_login\Desktop\base_yyyy-mm-dd.yml'' 
 +        * The environment can later be replicated (with the latest version of the requested packages) with:\\ ''conda env create -n existing_environment_clone -f some_path/existing_environment_yyyy-mm-dd.yml'' 
 +    * <wrap hi>''pip'' WARNING!</wrap> 
 +      * ''conda export'' will only export information about packages installed with ''conda install''. You should also check if you have installed packages with ''pip'' in your environment, and write it down... 
 +      * Linux/Mac example: 
 +        * <code>(base) > conda list -n test_env | grep pypi 
 +sbck                                    1.4.0            pypi_0                   pypi 
 +xsbck                                   1.0.0            pypi_0                   pypi 
 +(base) > conda list -n test_env | grep pypi > some_path/test_env_pypi_yyyy-mm-dd.txt</code> 
 +      * Windows example:  
 +        * <code>(base) PS C:\> conda list -n test_env | findstr pypi 
 +brotli                           1.1.0               pypi_0                   pypi 
 +(base) PS C:\> conda list -n test_env | findstr pypi >  C:\Users\your_login\Desktop\test_env_pypi_yyyy-mm-dd.txt</code> 
  
   * **Determine the relationship between installed packages**   * **Determine the relationship between installed packages**
other/uvcdat/cdat_conda/miniconda3_install.1755876252.txt.gz · Last modified: by jypeter

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki