Skip to content

Commit 6c7c95a

Browse files
ChrisBarker-NOAAwebknjaz
authored andcommitted
updated notes on conda.
1 parent 3bbc47f commit 6c7c95a

File tree

1 file changed

+22
-18
lines changed

1 file changed

+22
-18
lines changed

source/key_projects.rst

Lines changed: 22 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -404,26 +404,30 @@ conda
404404

405405
:doc:`Docs <conda:index>`
406406

407-
conda is the package management tool for `Anaconda
408-
<https://docs.anaconda.com/anaconda/>`__ Python installations.
409-
Anaconda Python is a distribution from `Anaconda, Inc
410-
<https://www.anaconda.com/products/individual>`__ specifically aimed at the scientific
411-
community, and in particular on Windows where the installation of binary
412-
extensions is often difficult.
407+
Conda is a package, dependency, and environment management system for any language — Python, R,
408+
Ruby, C/C++, Fortran, and more. It is written in Python and
409+
widely used in the Python scientific computing community, due to its support for non-Python
410+
compiled libraries and extensions. It is used as the basis of the `Anaconda
411+
<https://docs.anaconda.com/anaconda/>`__ Python distribution from `Anaconda, Inc.specifically
412+
aimed at the scientific community, community, but can also be used on its own, or with the
413+
:doc:`miniconda <conda:miniconda>`, `miniforge <https://github.com/conda-forge/miniforge>`_ or
414+
`pixi <https://pixi.sh/>`_ systems. It is available for Windows, Mac and Linux systems.
413415

414416
Conda is a completely separate tool from :ref:`pip`, virtualenv and wheel, but provides
415-
many of their combined features in terms of package management, virtual environment
416-
management and deployment of binary extensions.
417-
418-
Conda does not install packages from PyPI and can install only from
419-
the official Anaconda repositories, or anaconda.org (a place for
420-
user-contributed *conda* packages), or a local (e.g. intranet) package
421-
server. However, note that :ref:`pip` can be installed into, and work
422-
side-by-side with conda for managing :term:`distributions
423-
<Distribution Package>` from PyPI. Also, `conda skeleton
424-
<https://docs.conda.io/projects/conda-build/en/latest/user-guide/tutorials/build-pkgs-skeleton.html>`__
425-
is a tool to make Python packages installable by conda by first
426-
fetching them from PyPI and modifying their metadata.
417+
many of their combined features, such as package management, virtual environment
418+
management and deployment of binary extensions and other binary code.
419+
420+
Conda does not install packages from PyPI -- it can only manage packages built specifically
421+
for conda, which can be made available on a "conda channel", such as those hosted on
422+
`anaconda.org <https://anaconda.org/>`__ or a local (e.g. intranet) package server.
423+
In addition to the "default" channels managed by `Anaconda, Inc. <https://www.anaconda.com/>`__, there are a wide variety of packages from the community supported
424+
`conda-forge project <https://conda-forge.org/>`__
425+
426+
Note that :ref:`pip` can be installed into, and work side-by-side with conda
427+
for managing :term:`distributions <Distribution Package>` from PyPI. It is also possible
428+
to build conda packages from Python source packages using tools such as
429+
`conda skeleton
430+
<https://docs.conda.io/projects/conda-build/en/latest/user-guide/tutorials/build-pkgs-skeleton.html>`__: a tool to automatically make conda packages from Python packages available on PyPI.
427431

428432
.. _devpi:
429433

0 commit comments

Comments
 (0)