the conda-forge blog

We do a lot of things but only blog about some of them.

Here are some recent selections.

  • R 4.0 Migration Retrospective - C.J. Wright, Matthew R. Becker, 2020-07-11

    While the R 4.0 migration has been functionally complete for quite a while, the recent migration of r-java and its dependents gives a good opportunity to write a retrospective on the technical issues with large-scale migrations in conda-forge and how we solved them.

  • Scipy 2020 Packaging BOF - C.J. Wright, 2020-07-02

    Have some thoughts about conda-forge and how it can be expanded in a way that is sustainable? Join us in this virtual Birds of a Feather discussion where we’ll discuss maintenance, pain points, opportunities within conda-forge. Any and all are welcome, and we especially are seeking new viewpoints and opinions!

  • Conda-Forge Operational Risk - C.J. Wright, 2020-07-02

    Recently I’ve been thinking about operational risk (op. risk). Operational risks arise from failures of processes, for instance a missing email, or an automated software system not running properly. Many commercial institutions are interested in minimizing op. risk, since it is risk that produces no value, as opposed to risks associated with investing. This is also something I think about in my job at Lab49, where I’m a software engineering consultant focusing on financial institutions. I think there is also a good analogy for Conda-Forge, even though we are not a commercial outfit. In this case the risk we incur isn’t the potential for lost earnings but frustration for our users and maintainers in the form of bugs and lackluster user experience. In this post I explore three main sources of operational risk for Conda-Forge: Automation, Top-Down Control, and Self-Service Structure.

  • PyPy builds on conda-forge - Isuru Fernando, 2020-03-10

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

  • Google Summer of Code 2020 improved automatic maintenance of conda-forge - Filipe Pires Alvarenga Fernandes, 2020-02-04

    The conda-forge “autotick” bot is a crucial part of conda-forge’s infrastructure. It enables automatic maintenance of conda-forge packages by pushing version updates to the underlying software and enabling large migrations of packages from one dependency to another (e.g., Python 3.7 to Python 3.8). As conda-forg grows in size, with over 9,000 packages to date, automatic maintenance of the conda-forge ecosystem will become even more important.