9 posts tagged with "infrastructure"

conda-forge now has partial experimental support for Windows on Arm64 platform. To use the conda-forge packages on an arm64 machine running windows, you first have to install Miniforge for Windows x86_64 since miniforge does not support Windows arm64 yet. Then you can do

set "CONDA_SUBDIR=win-arm64"
conda create -n newenv python
conda activate newenv

This gives you a minimal python environment. You can play around with this untested python binary and provide feedback.

Today marks 100 days since the official release of Python 3.14, and we're thrilled to report that conda-forge has achieved its fastest Python version adoption ever. With 1,932 binary packages available at the 100-day mark, Python 3.14 has surpassed all previous Python releases in early availability.

Earlier this month, Anaconda announced that they are deprecating the r channel bundled in the defaults multichannel. This decision does not impact R packages in conda-forge, which continue to be available without any changes.

On macOS, conda-forge has provided clang, clangxx as the sole compiler for C and C++ sources. We have also provided gfortran to compile FORTRAN sources. Unlike other package managers like homebrew we have not provided gcc nor g++ on macos. The reason to not provide those have been to avoid incompatibility with the clang based toolchain and also the maintenance burden. There are two main incompatibilities. First, clang++ uses libc++ as the standard C++ library and g++ uses libstdc++ as the standard C++ library. Second, clang uses libomp as the OpenMP library whereas gcc uses libgomp as the OpenMP library.

Today, we announce the availability of gcc, g++ compilers on macos. You can install them using:

conda install gcc gxx

Currently we support only gcc 15 and will not support gcc 14 or previous versions.

With yesterday's release of Python 3.14, we not only have Python 3.14 itself available on conda-forge, but also a wide selection of packages to make use of it. As the conda ecosystem is based on binary packages, this means that several packages are already built for Python 3.14.

You can create a new environment by using:

conda create -n py314 python=3.14 -c conda-forge

At the time of writing, the Python 3.14 migration is 77% progressed. This means that:

• 1273 (41%) packages that needed a rebuild were built for Python 3.14
• 1115 (36%) have an open PR to get rebuilt for Python 3.14
• 704 (23%) packages are still waiting for a dependency to be rebuilt.

The conda-forge team is excited to announce that the v1 recipe format is available on conda-forge. The v1 recipe format is a community initiative dating back over 3 years to improve the recipe format for conda packages. If you are a maintainer of a feedstock on conda-forge, you have probably dealt with meta.yaml files that conda-build utilizes. The file format has some limitations which is why the community has come together to come up with an improved version of the format: the v1 format.

We introduce noarch variants for python packages on conda-forge that have compiled extensions but with pure python reference implementations to make life easier for early adopters of new python variants.

conda-forge now supports Python 3.13 on conda. You can create a new environment with Python 3.13 by running the command:

conda create -n py313 python=3.13 -c conda-forge

conda-forge now supports PyPy3.6 as the python interpreter in a conda environment

Supported platforms are,

• Linux-x86_64 (glibc 2.12 or newer)
• OSX-x86_64 (OSX 10.9 or newer)
• Linux-aarch64 (glibc 2.17 or newer)
• Linux-ppc64le (glibc 2.17 or newer)