[Mlir-commits] [llvm] [mlir] [mlir python] Add nanobind support for standalone dialects. (PR #117922)

[Marius Brehler]

marbre wrote:

> If that is a hard requirement, we will probably need to exclude the python packages from distribution in OS packages (they were never scoped for this anyway) or move them out of tree. The python ecosystem is simply moving too fast to gate on this. We cannot stay in sync with python.org development without being able to use bleeding edge deps in the bindings.

>From packaging for Linux distributions, I agree that there is a strong need to only consume dependencies that are packaged for the OS. However, as long as one can disable `FetchContent` without needing to patch the `CMakeLists.txt` by a build option it should okay to provide getting nanobind via `FetchContent` as an option. With this it isn't enforced and distributions can build upon what is shipped for the OS. If they don't ship the dep they still can exclude the python package to not pull in a dependency during build time.

https://github.com/llvm/llvm-project/pull/117922