Differences

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

--- other:uvcdat:cdat_conda:miniforge_install [2025/10/06 16:54] – [Why should you use Miniconda3 ?] Updated version, now that we use miniforge instead of miniconda jypeter
+++ other:uvcdat:cdat_conda:miniforge_install [2026/10/19 11:32] (current) – [Useful conda commands] jypeter
@@ Line 501: / Line 501: @@
 <WRAP center round important 60%>
-It seems **safe** to reclaim some disk space by cleaning up the initial (//base//) installation, **when no other (shared) environments have been installed yet**\\ \\ Use cleaning with caution after installing other environments (besides ''base''), especially environments **shared** by several users. But it should not break your installation
+  * **''conda'' does not remove old/unused packages**, and a distribution with lots of packages may grow a lot, and exceed disk and/or files quotas, if you do not clean it from time to time
+  * Use cleaning with caution after installing other environments (besides ''base''), especially environments **shared** by several users. But it should not break your installation
 </WRAP>
@@ Line 508: / Line 510: @@
     * There is **no ''-n'' option to specify an environment name**, because ''clean'' will //Remove **unused** packages and caches// shared by **all** the environments
       * The ''clean'' command will mostly deal with the content of the ''/path_to_miniconda/pkgs/'' directory
-    * Example:<code>(base) $ conda clean --all
+    * Example 1: cleaning during the initial installation<code>(base) $ conda clean --all
 Will remove 154 (180.9 MB) tarball(s).
 Proceed ([y]/n)? y
@@ Line 523: / Line 525: @@
 (base) $ du -sh /homedata/jypmce/miniconda3_2024-03
 M    /homedata/jypmce/miniconda3_2024-03
+</code>
+    * Example 2: **exceeding files quotas** (in the same installation) after forgetting to clean regularly<code>$ quotas
+     Filesystem    used   quota   limit   grace   files   quota   limit   grace
+      /homedata  16.59G      1T    1.1T       -  339671* 300000  350000 5d39m28s
+$ conda clean --all
+Will remove 563 (1.85 GB) tarball(s).
+Proceed ([y]/n)? y
+Will remove 1 index cache(s).
+Proceed ([y]/n)? y
+Will remove 592 (8.25 GB) package(s).
+Proceed ([y]/n)? y
+There are no tempfile(s) to remove.
+There are no logfile(s) to remove.
+$ quotas
+     Filesystem    used   quota   limit   grace   files   quota   limit   grace
+      /homedata  5.291G      1T    1.1T       -  141557  300000  350000       -
+$ du -sh /homedata/jypmce/miniconda3_2024-03
+.2G    /homedata/jypmce/miniconda3_2024-03
 </code>
@@ Line 748: / Line 774: @@
       * Same as ''conda //uninstall// package1 package2 packageN''
     * Matching ''pip'' commands (**only** if the package is not available in conda!)
-      * ''pip install package''
+      * **First**:
-      * ''pip uninstall package''
+        * Try: ''conda pypi install package''
+        * More details why you should do that in the [[#conda_pip_and_virtualenv|conda vs pip]] section
+      * Otherwise:
+        * ''pip install package''
+        * ''pip uninstall package''
   * **Update a package** in the current, or a specific environment
@@ Line 844: / Line 874: @@
 ==== conda, pip and virtualenv ====
+  * May 2026: [[https://conda.org/blog/2026-05-07-conda-and-pip-ecosystems|Conda and pip are two ecosystems, not just tools]]
+  * June 2026: [[https://conda.org/blog/2026-06-25-bridging-conda-and-pypi-ecosystems/|Bridging conda and PyPI ecosystems: Install PyPI packages with conda install]]
   * Read the [[https://docs.conda.io/projects/conda/en/stable/commands/#conda-vs-pip-vs-virtualenv-commands|Conda vs. pip vs. virtualenv commands]] section