[mlir][Python] Bump MLIR Python minimum version to 3.10 - #163499
Merged
Conversation
makslevental
force-pushed
the
users/makslevental/bump-python-3.10
branch
from
November 11, 2025 18:14
9b4faa7 to
0e1862e
Compare
makslevental
force-pushed
the
users/makslevental/bump-python-3.10
branch
from
January 4, 2026 17:37
0e1862e to
0c71423
Compare
Contributor
Author
makslevental
requested review from
boomanaiden154,
ftynse,
jpienaar,
rengolin and
rolfmorel
January 5, 2026 01:11
makslevental
marked this pull request as ready for review
January 5, 2026 01:12
Member
|
@llvm/pr-subscribers-mlir Author: Maksim Levental (makslevental) ChangesThis PR bumps the minimum Python version required for MLIR to be Python 3.10. Full diff: https://github.com/llvm/llvm-project/pull/163499.diff 1 Files Affected:
diff --git a/mlir/cmake/modules/MLIRDetectPythonEnv.cmake b/mlir/cmake/modules/MLIRDetectPythonEnv.cmake
index fb0fbf3457ade..098d12aedeb91 100644
--- a/mlir/cmake/modules/MLIRDetectPythonEnv.cmake
+++ b/mlir/cmake/modules/MLIRDetectPythonEnv.cmake
@@ -1,5 +1,6 @@
# Macros and functions related to detecting details of the Python environment.
+set(MLIR_MINIMUM_PYTHON_VERSION 3.10)
# Finds and configures python packages needed to build MLIR Python bindings.
macro(mlir_configure_python_dev_packages)
if(NOT MLIR_DISABLE_CONFIGURE_PYTHON_DEV_PACKAGES)
@@ -8,7 +9,7 @@ macro(mlir_configure_python_dev_packages)
# package. This seems to work around cmake bugs searching only for
# Development.Module in some environments. However, in other environments
# it may interfere with the subsequent search for Development.Module.
- find_package(Python3 ${LLVM_MINIMUM_PYTHON_VERSION}
+ find_package(Python3 ${MLIR_MINIMUM_PYTHON_VERSION}
COMPONENTS Interpreter Development)
endif()
@@ -19,7 +20,7 @@ macro(mlir_configure_python_dev_packages)
# See https://pybind11.readthedocs.io/en/stable/compiling.html#findpython-mode
set(_python_development_component Development.Module)
- find_package(Python3 ${LLVM_MINIMUM_PYTHON_VERSION}
+ find_package(Python3 ${MLIR_MINIMUM_PYTHON_VERSION}
COMPONENTS Interpreter ${_python_development_component} REQUIRED)
# We look for both Python3 and Python, the search algorithm should be
@@ -39,7 +40,7 @@ macro(mlir_configure_python_dev_packages)
# It's a little silly to detect Python a second time, but nanobind's cmake
# code looks for Python_ not Python3_.
- find_package(Python ${LLVM_MINIMUM_PYTHON_VERSION}
+ find_package(Python ${MLIR_MINIMUM_PYTHON_VERSION}
COMPONENTS Interpreter ${_python_development_component} REQUIRED)
unset(_python_development_component)
|
boomanaiden154
approved these changes
Jan 5, 2026
boomanaiden154
left a comment
Contributor
There was a problem hiding this comment.
This LGTM as long as all of the bots building MLIR have greater than the minimum Python version.
Please link the RFC from the description as that's where the discussion actually happened.
mahesh-attarde
pushed a commit
to mahesh-attarde/llvm-project
that referenced
this pull request
Jan 6, 2026
This PR bumps the minimum Python version required for MLIR to be Python 3.10. See https://discourse.llvm.org/t/rfc-adopt-regularly-scheduled-python-minimum-version-bumps/88841 for a discussion about the expected bump schedule going forward.
kuhar
pushed a commit
that referenced
this pull request
Feb 27, 2026
According to PR #163499, minimum Python version for mlir-py is now 3.10, we no longer need patches for py<=3.9. This change aligns with the Python version bump policy discussed [here](https://discourse.llvm.org/t/rfc-adopt-regularly-scheduled-python-minimum-version-bumps/88841).
kuhar
pushed a commit
to iree-org/llvm-project
that referenced
this pull request
Mar 1, 2026
According to PR llvm#163499, minimum Python version for mlir-py is now 3.10, we no longer need patches for py<=3.9. This change aligns with the Python version bump policy discussed [here](https://discourse.llvm.org/t/rfc-adopt-regularly-scheduled-python-minimum-version-bumps/88841).
RattataKing
added a commit
to iree-org/llvm-project
that referenced
this pull request
Mar 2, 2026
According to PR llvm#163499, minimum Python version for mlir-py is now 3.10, we no longer need patches for py<=3.9. This change aligns with the Python version bump policy discussed [here](https://discourse.llvm.org/t/rfc-adopt-regularly-scheduled-python-minimum-version-bumps/88841).
sujianIBM
pushed a commit
to sujianIBM/llvm-project
that referenced
this pull request
Mar 5, 2026
According to PR llvm#163499, minimum Python version for mlir-py is now 3.10, we no longer need patches for py<=3.9. This change aligns with the Python version bump policy discussed [here](https://discourse.llvm.org/t/rfc-adopt-regularly-scheduled-python-minimum-version-bumps/88841).
This was referenced Apr 15, 2026
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.
This PR bumps the minimum Python version required for MLIR to be Python 3.10. See https://discourse.llvm.org/t/rfc-adopt-regularly-scheduled-python-minimum-version-bumps/88841 for a discussion about the expected bump schedule going forward.