Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .github/workflows/pipeline.yml
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ jobs:
- name: Setup Mambaforge
uses: conda-incubator/setup-miniconda@v3
with:
python-version: "3.12"
python-version: "3.13"
miniforge-version: latest
channels: conda-forge
conda-remove-defaults: "true"
Expand All @@ -174,7 +174,7 @@ jobs:
- name: Setup Mambaforge
uses: conda-incubator/setup-miniconda@v3
with:
python-version: "3.12"
python-version: "3.13"
miniforge-version: latest
channels: conda-forge
conda-remove-defaults: "true"
Expand Down Expand Up @@ -202,7 +202,7 @@ jobs:
cat .ci_support/environment-mpich.yml
- uses: conda-incubator/setup-miniconda@v3
with:
python-version: '3.12'
python-version: '3.13'
miniforge-version: latest
channels: conda-forge
conda-remove-defaults: "true"
Expand Down Expand Up @@ -233,7 +233,7 @@ jobs:
cat .ci_support/environment-openmpi.yml
- uses: conda-incubator/setup-miniconda@v3
with:
python-version: '3.12'
python-version: '3.13'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

flux-core 0.81.0 Python 3.13 support compatibility

💡 Result:

Short answer: No — flux-core 0.81.0 does not list official Python 3.13 support.

Evidence:

  • flux-core 0.81.0 release notes (published Dec 2–3, 2025) make no mention of Python 3.13 support. [1]
  • The project explicitly added Python 3.12 support in v0.59.0 (Feb 6, 2024), but later release notes and PyPI / flux-python artifacts for recent releases show wheels for CPython up to 3.11 (no cp313 wheel listed). [2][3]

If you need Python 3.13: you can either run flux-core with a supported Python (3.10–3.12/3.11 per the package artifacts) or try building the Python bindings from source against Python 3.13 (unsupported — may require patching). References: [1] flux-core v0.81.0 release notes; [2] flux-core v0.59.0 (Python 3.12 mention); [3] flux-python / PyPI wheel listings.


🌐 Web query:

flux-pmix 0.6.0 Python 3.13 support compatibility

💡 Result:

Short answer: flux-pmix 0.6.0 does not list official Python 3.13 support. flux-pmix is a Flux PMI plugin (C code) and does not itself declare a python_requires; Python compatibility for Flux features is governed by flux-core / flux-python, and the project added official Python 3.12 support (not 3.13) in flux-core releases. [1][2]

What to do next

  • If you need runtime Python integration, use a flux-core / flux-python build that matches your Python interpreter; current official notes show support through Python 3.12. Test on 3.13 in a separate environment if you must use it. [1][2]

Sources

  • flux-core release notes (Python 3.12 support). [1]
  • flux-pmix package listings / repository (release versions including 0.6.0). [2]

Downgrade to Python 3.12 — flux-core 0.81.0 and flux-pmix 0.6.0 do not support Python 3.13.

flux-core 0.81.0 does not list Python 3.13 support. Official wheels are only built for CPython up to 3.11, with Python 3.12 being the latest officially supported version. flux-pmix 0.6.0 follows the same constraint. Change line 236 to python-version: '3.12'.

🤖 Prompt for AI Agents
In .github/workflows/pipeline.yml around line 236, the workflow sets
python-version to '3.13' but flux-core 0.81.0 and flux-pmix 0.6.0 do not support
3.13; change the value to '3.12' so the CI uses Python 3.12; update the line to
python-version: '3.12' and commit the workflow change.

miniforge-version: latest
channels: conda-forge
conda-remove-defaults: "true"
Expand Down
Loading