#condaforge — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #condaforge, aggregated by home.social.
-
Totally normal workflow:
I work on documenting #Jinja syntax used in #CondaForge recipes.
https://github.com/conda-forge/conda-forge.github.io/pull/2782
I decide that the snippets would use Jinja syntax highlighting. However, #Prism doesn't have one. But Internets suggest Twig would work instead.
https://github.com/PrismJS/prism/issues/759
So I try Twig. Except that Twig highlighter crashes in #Docusaurus. But there's a workaround.
https://github.com/facebook/docusaurus/issues/8065
So I copy the code over to the project, fix it and while at it, rename it to "jinja" and adjust a bit.
But then, highlighting Jinja expressions alone looks pretty bleak, so let's combine it with YAML… Hmm, that actually doesn't work that well, needs some more adjustments. And before you know it, I have a pretty new Jinja highlighter, and a recipe highlighter that combines Jinja expressions, YAML, v0 recipe selectors, v1 if:/skip: conditions, and also highlighting shell / cmd variables for a good measure.
https://github.com/conda-forge/conda-forge.github.io/pull/2790
-
I'm looking at Repology, and I think most of the distributions and other downstreams have rightfully boycotted #Python #chardet #copywashing. Of course, there's the possibility that some of them are simply out-of-date, though.
So far chardet-7 is distributed by #Chromebrew, #CondaForge (not on Repology), #Homebrew, #KaOS, #OpenIndiana, #openmamba, #Ravenports, #Spack and #T2 SDE. Shame on you!
https://repology.org/project/chardet/versions
https://repology.org/project/python%3Achardet/versions -
I'm looking at Repology, and I think most of the distributions and other downstreams have rightfully boycotted #Python #chardet #copywashing. Of course, there's the possibility that some of them are simply out-of-date, though.
So far chardet-7 is distributed by #Chromebrew, #CondaForge (not on Repology), #Homebrew, #KaOS, #OpenIndiana, #openmamba, #Ravenports, #Spack and #T2 SDE. Shame on you!
https://repology.org/project/chardet/versions
https://repology.org/project/python%3Achardet/versions -
I'm looking at Repology, and I think most of the distributions and other downstreams have rightfully boycotted #Python #chardet #copywashing. Of course, there's the possibility that some of them are simply out-of-date, though.
So far chardet-7 is distributed by #Chromebrew, #CondaForge (not on Repology), #Homebrew, #KaOS, #OpenIndiana, #openmamba, #Ravenports, #Spack and #T2 SDE. Shame on you!
https://repology.org/project/chardet/versions
https://repology.org/project/python%3Achardet/versions -
I'm looking at Repology, and I think most of the distributions and other downstreams have rightfully boycotted #Python #chardet #copywashing. Of course, there's the possibility that some of them are simply out-of-date, though.
So far chardet-7 is distributed by #Chromebrew, #CondaForge (not on Repology), #Homebrew, #KaOS, #OpenIndiana, #openmamba, #Ravenports, #Spack and #T2 SDE. Shame on you!
https://repology.org/project/chardet/versions
https://repology.org/project/python%3Achardet/versions -
I'm looking at Repology, and I think most of the distributions and other downstreams have rightfully boycotted #Python #chardet #copywashing. Of course, there's the possibility that some of them are simply out-of-date, though.
So far chardet-7 is distributed by #Chromebrew, #CondaForge (not on Repology), #Homebrew, #KaOS, #OpenIndiana, #openmamba, #Ravenports, #Spack and #T2 SDE. Shame on you!
https://repology.org/project/chardet/versions
https://repology.org/project/python%3Achardet/versions -
Another post on #Quansight PBC blog: "BLAS/LAPACK #packaging"
https://labs.quansight.org/blog/blas-lapack-packaging
"""
#BLAS and #LAPACK are the standard libraries for linear algebra. The original implementation, often called Netlib LAPACK, developed since the 1980s, nowadays serves primarily as the origin of the standard interface, the reference implementation and a conformance test suite. The end users usually use optimized implementations of the same interfaces. The choice ranges from generically tuned libraries such as OpenBLAS and BLIS, through libraries focused on specific hardware such as Intel® oneMKL, Arm Performance Libraries or the Accelerate framework on macOS, to ATLAS that aims to automatically optimize for a specific system.The diversity of available libraries, developed in parallel with the standard interfaces, along with vendor-specific extensions and further downstream changes, adds quite a bit of complexity around using these libraries in software, and distributing such software afterwards. This problem entangles implementation authors, consumer software authors, build system maintainers and distribution maintainers. Software authors generally wish to distribute their packages built against a generically optimized BLAS/LAPACK implementation. Advanced users often wish to be able to use a different implementation, more suited to their particular needs. Distributions wish to be able to consistently build software against their system libraries, and ideally provide users the ability to switch between different implementations. Then, build systems need to provide the scaffolding for all of that.
I have recently taken up the work to provide such a scaffolding for the Meson build system; to add support for BLAS and LAPACK dependencies to Meson. While working on it, I had to learn a lot about BLAS/LAPACK packaging: not only how the different implementations differ from one another, but also what is changed by their respective downstream packaging. In this blog post, I would like to organize and share what I have learned.
""" -
🔄 Update: I’ve just expanded my #Miniforge migration guide with a dedicated troubleshooting section. It now covers common issues I’ve encountered over the past years — including #SSL certificate errors, channel configuration for conda-forge-only environments, and a workaround for situations where #mamba isn’t available in the base environment. If you have further tips, feel free to comment here or on the blog post. #conda #CondaForge
-
After recent license changes at #Anaconda, Inc., #Miniforge has become the recommended, fully open solution for institutional #Python environments. Now bundling both #conda and #mamba, it replaces #Miniconda/ #Mambaforge, ensuring high performance and broad package access via #CondaForge. Here I summarized the key changes and migration steps:
🌍 https://www.fabriziomusacchio.com/blog/2025-07-03-miniforge/
-
After recent license changes at #Anaconda, Inc., #Miniforge has become the recommended, fully open solution for institutional #Python environments. Now bundling both #conda and #mamba, it replaces #Miniconda/ #Mambaforge, ensuring high performance and broad package access via #CondaForge. Here I summarized the key changes and migration steps:
🌍 https://www.fabriziomusacchio.com/blog/2025-07-03-miniforge/
-
After recent license changes at #Anaconda, Inc., #Miniforge has become the recommended, fully open solution for institutional #Python environments. Now bundling both #conda and #mamba, it replaces #Miniconda/ #Mambaforge, ensuring high performance and broad package access via #CondaForge. Here I summarized the key changes and migration steps:
🌍 https://www.fabriziomusacchio.com/blog/2025-07-03-miniforge/
-
After recent license changes at #Anaconda, Inc., #Miniforge has become the recommended, fully open solution for institutional #Python environments. Now bundling both #conda and #mamba, it replaces #Miniconda/ #Mambaforge, ensuring high performance and broad package access via #CondaForge. Here I summarized the key changes and migration steps:
🌍 https://www.fabriziomusacchio.com/blog/2025-07-03-miniforge/
-
After recent license changes at #Anaconda, Inc., #Miniforge has become the recommended, fully open solution for institutional #Python environments. Now bundling both #conda and #mamba, it replaces #Miniconda/ #Mambaforge, ensuring high performance and broad package access via #CondaForge. Here I summarized the key changes and migration steps:
🌍 https://www.fabriziomusacchio.com/blog/2025-07-03-miniforge/
-
@ashwinvis I have heard that #Anaconda is starting to shakedown larger academic institutes (most easily exceed the 200 employee threshold) using the default channel - at least one is looking at blocking use via their firewall as part of avoiding this!
Time to switch from #MiniConda etc to #MiniForge https://github.com/conda-forge/miniforge where the #CondaForge channel is set as the default (and only) channel.
-
@ashwinvis I have heard that #Anaconda is starting to shakedown larger academic institutes (most easily exceed the 200 employee threshold) using the default channel - at least one is looking at blocking use via their firewall as part of avoiding this!
Time to switch from #MiniConda etc to #MiniForge https://github.com/conda-forge/miniforge where the #CondaForge channel is set as the default (and only) channel.
-
@ashwinvis I have heard that #Anaconda is starting to shakedown larger academic institutes (most easily exceed the 200 employee threshold) using the default channel - at least one is looking at blocking use via their firewall as part of avoiding this!
Time to switch from #MiniConda etc to #MiniForge https://github.com/conda-forge/miniforge where the #CondaForge channel is set as the default (and only) channel.
-
@ashwinvis I have heard that #Anaconda is starting to shakedown larger academic institutes (most easily exceed the 200 employee threshold) using the default channel - at least one is looking at blocking use via their firewall as part of avoiding this!
Time to switch from #MiniConda etc to #MiniForge https://github.com/conda-forge/miniforge where the #CondaForge channel is set as the default (and only) channel.
-
@ashwinvis I have heard that #Anaconda is starting to shakedown larger academic institutes (most easily exceed the 200 employee threshold) using the default channel - at least one is looking at blocking use via their firewall as part of avoiding this!
Time to switch from #MiniConda etc to #MiniForge https://github.com/conda-forge/miniforge where the #CondaForge channel is set as the default (and only) channel.
-
Starting today, you can install iosacal with conda. This adds to the existing installation procedure with pip. Conda is a good fit for complex projects and has better tooling for reproducibility.
Installing iosacal can be achieved by adding conda-forge to your channels with:
conda config --add channels conda-forge conda config --set channel_priority strictOnce the conda-forge channel has been enabled, iosacal can be installed with conda:
conda install iosacalor with mamba:
mamba install iosacal