Skip to main content

conda-forge core meeting 2023-10-04

Add new agenda items under the Your __new__() agenda items heading


NameInitialsGitHub IDAffiliation
Dave ClementsDPCtnabtafAnaconda
Daniel ChingDJCcarterboxArgonne National Laboratory
Marcel BargullMBmbargullBioconda/cf
John KirkhamJKjakirkhamNVIDIA/cf
Eric DillEDericdillAnaconda/cf
Filipe FernandesFFocefpafconda-forge
Carl AndersonCPAbaraboAnaconda
Matt BeckerMRBbeckermrcf

15 people total

Standing items

  • [ ]

From previous meeting(s)

Active votes

  • [ ]

Your __new__() agenda items

  • (HV) Drop PyPy on aarch/ppc?

    • PyPy support is already stretched very thin, to the point that we considered dropping it (c.f. here), haven't done a pypy3.10 migration yet, various high impact bugs remain, etc.
    • We have no CI on the feedstock for aarch/ppc (cannot cross-compile, travis times out), and manual builds put extra strain on maintenance, and sometimes just don't happen (e.g. missing 7.3.12 & 7.3.13, the last two versions), meaning missed bugfixes etc.
    • Rather than risk PyPy support overall by overwhelming the PyPy devs (or demanding that someone from core do manual builds for every PR), I suggest to drop PyPy on aarch/ppc; usage numbers for those builds are on the order of 1 in 10'000 users. This is not great, but IMO more sensible vis-à-vis the very constrained PyPy-resources.
    • Isuru does these builds. This is not causing larger problems in CF, therefore, it's up to maintainers (Isuru) to make this decision?
    • Axel: But it has been a problem for some downstream packages.
    • Axel: will report problems as they arise.
    • AI: If we want to drop PyPy ARM/PPC, raise an issue on the webpage repo or pinning repo to discuss
  • (HV) Compiler bump: GCC 13 & Clang 16

    • PR is ready, relevant info in the OP.
    • Isuru: Clang 16 now, GCC 13 in a bit.
  • (JRG) Intention to submit a CZI EOSS6 letter of intent with Wolf.

    • Rough draft:
    • Theme: the future of conda-build, transitioning to new tooling (boa, rattler-build) and improved build reproducibility in conda-forge.
    • Interested in knowing if this is a terrible idea.
    • Deadline: Oct 16th.
  • (JRG) GPU CI status:

  • (IF) m2-recipes

  • (WV) Sovereign Tech Fund contract

    • libsolv - Rust port
    • rattler-build conda-forge integration
    • conda-forge reproducibility evaluation
  • (WV) Please don't forget to vote for conda steering council :)

Pushed to next meeting

  • [ ]


  • [ ]