Differences

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

--- other:uvcdat:cdat_conda:miniconda3_install [2025/07/29 16:36] – [Installation history] Updated the examples jypeter
+++ other:uvcdat:cdat_conda:miniconda3_install [2025/09/17 14:24] (current) – [Useful conda commands] More export details jypeter
@@ Line 622: / Line 622: @@
   * **Available environments**
     * ''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
 # conda environments:
@@ Line 713: / Line 713: @@
     * ''conda update -n existing_environment %%--%%all''
     * [[#the_first_time_we_update_miniconda3|'base' environment update example]]
+  * **Export the description of an environment** (as a checkpoint, or to replicate the environment somewhere else)
+    * 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**
@@ Line 877: / Line 896: @@
     * The link also shows how to do it with standard Linux tools (find, grep), based on the [[https://docs.conda.io/projects/conda-build/en/stable/resources/package-spec.html#conda-package-specification|Conda package specification]] page
     * [[https://github.com/kelvinou01/conda-which|conda-which]] seems to work (see [[https://github.com/conda/conda/issues/14026#issuecomment-2268821608|test / example]]) !
+      * Note: ''conda-which'' **has to be (obviously) installed in the ''base'' environment**
 /* standard page footer */