Support Python 3.12-3.14 in Conda builds - #70
Merged
Merged
Conversation
jimboid
approved these changes
Sep 29, 2026
jimboid
left a comment
Member
There was a problem hiding this comment.
Fixes a major annoyance with code not installing on different versions of python despite them bring listed in meta.yaml/pyptoject.toml in the conda release chain. Happy to merge, you will want to release at some point to reflect the change.
harryswift01
deleted the
69-general-support-multiple-python-versions
branch
September 29, 2026 10:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR makes the Conda package actually installable across all supported Python versions (3.12, 3.13, 3.14), previously the recipe only ever built and published a single Python 3.14 variant regardless of what
meta.yamlclaimed to support.Changes
Declare the Python build matrix in the Conda recipe:
conda-recipe/conda_build_config.yamldeclaringpython: ["3.12", "3.13", "3.14"], the standard conda-forge/bioconda way of expressing a multi-version build matrixmeta.yaml'shost/testsections to a bare, unconstrainedpythonso conda-build's variant system actually substitutes the target version, an explicit range there (the previouspython >=3.12) silently blocks this substitutionrun: python >=3.12,<3.15withpyproject.toml'srequires-pythonPublish all Python/platform combinations on release:
release.yaml'scondajob back to anos-only matrix, since a singleconda buildnow produces all three Python variants per platform automaticallySimplify weekly regression testing to match:
python-versionmatrix fromweekly-regression.yaml, each OS job now builds and tests all three variants in one runtimeout-minutesfrom 30 to 90 to account for the extra build/test work per jobFix stale documentation:
installation.rst/development.rstfrom "Python 3.12 or later" to "Python 3.12, 3.13, or 3.14" to match the actual supported rangeImpact
conda_build_config.yaml's default matrix and via explicit--pythonoverrides