From f6f89b6d398851a339de043adaa2d4e26459b963 Mon Sep 17 00:00:00 2001 From: "Alexander V. Hopp" Date: Mon, 30 Mar 2026 15:11:51 +0200 Subject: [PATCH 1/3] Pin onnxruntime version due to lacking python 3.10 support --- pyproject.toml | 2 +- uv.lock | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/pyproject.toml b/pyproject.toml index 5afec4efa7..9ee8596b50 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -75,7 +75,7 @@ chem = [ onnx = [ "onnx>=1.16.0", # see AUDIT NOTE, required by skl2onnx - "onnxruntime>=1.15.1", + "onnxruntime>=1.15.1,<1.24", "skl2onnx>=1.19.1", ] diff --git a/uv.lock b/uv.lock index a14900db8e..b6efe2b8c0 100644 --- a/uv.lock +++ b/uv.lock @@ -427,7 +427,7 @@ requires-dist = [ { name = "ngboost", marker = "extra == 'extras'", specifier = ">=0.3.12,<1" }, { name = "numpy", specifier = ">=1.24.1,<3" }, { name = "onnx", marker = "extra == 'onnx'", specifier = ">=1.16.0" }, - { name = "onnxruntime", marker = "extra == 'onnx'", specifier = ">=1.15.1" }, + { name = "onnxruntime", marker = "extra == 'onnx'", specifier = ">=1.15.1,<1.24" }, { name = "openpyxl", marker = "extra == 'examples'", specifier = ">=3.0.9" }, { name = "pandas", specifier = ">=1.4.2,<3" }, { name = "pandas-stubs", marker = "extra == 'mypy'", specifier = ">=2.2.2.240603" }, From a514e33c09db964e534a71d410718b9daf052dc1 Mon Sep 17 00:00:00 2001 From: "Alexander V. Hopp" Date: Mon, 30 Mar 2026 15:34:24 +0200 Subject: [PATCH 2/3] Only pin for Python 3.10 --- pyproject.toml | 9 ++++++++- uv.lock | 3 ++- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/pyproject.toml b/pyproject.toml index 9ee8596b50..aff5ea1356 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -73,9 +73,16 @@ chem = [ "scikit-fingerprints>=1.13.1", ] +# NOTE: There is an error in the metadata of onnxruntim version 1.24.1 to 1.24.3. +# The metadata claims that these versions are compatible with Python 3.10. +# However, Python 3.10 is not actually supported by versions >=1.24. +# As this causes issues with dependency resolving, we explicitly set the upper bound +# for onnxruntime to <1.24 for Python 3.10. +# See https://github.com/microsoft/onnxruntime/pull/27354 for more details. onnx = [ "onnx>=1.16.0", # see AUDIT NOTE, required by skl2onnx - "onnxruntime>=1.15.1,<1.24", + "onnxruntime>=1.15.1,<1.24; python_version < '3.11'", + "onnxruntime>=1.15.1; python_version >= '3.11'", "skl2onnx>=1.19.1", ] diff --git a/uv.lock b/uv.lock index b6efe2b8c0..59aadbaffc 100644 --- a/uv.lock +++ b/uv.lock @@ -427,7 +427,8 @@ requires-dist = [ { name = "ngboost", marker = "extra == 'extras'", specifier = ">=0.3.12,<1" }, { name = "numpy", specifier = ">=1.24.1,<3" }, { name = "onnx", marker = "extra == 'onnx'", specifier = ">=1.16.0" }, - { name = "onnxruntime", marker = "extra == 'onnx'", specifier = ">=1.15.1,<1.24" }, + { name = "onnxruntime", marker = "python_full_version >= '3.11' and extra == 'onnx'", specifier = ">=1.15.1" }, + { name = "onnxruntime", marker = "python_full_version < '3.11' and extra == 'onnx'", specifier = ">=1.15.1,<1.24" }, { name = "openpyxl", marker = "extra == 'examples'", specifier = ">=3.0.9" }, { name = "pandas", specifier = ">=1.4.2,<3" }, { name = "pandas-stubs", marker = "extra == 'mypy'", specifier = ">=2.2.2.240603" }, From bd9e2fc54f78ba60bb837ec25196b8bae5120723 Mon Sep 17 00:00:00 2001 From: "Alexander V. Hopp" Date: Tue, 31 Mar 2026 17:13:04 +0200 Subject: [PATCH 3/3] Fix typo in pyproject.toml Co-authored-by: AdrianSosic --- pyproject.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pyproject.toml b/pyproject.toml index aff5ea1356..7326b4d6fc 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -73,7 +73,7 @@ chem = [ "scikit-fingerprints>=1.13.1", ] -# NOTE: There is an error in the metadata of onnxruntim version 1.24.1 to 1.24.3. +# NOTE: There is an error in the metadata of onnxruntime version 1.24.1 to 1.24.3. # The metadata claims that these versions are compatible with Python 3.10. # However, Python 3.10 is not actually supported by versions >=1.24. # As this causes issues with dependency resolving, we explicitly set the upper bound