5 posts tagged with "infrastructure"

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)