Python bindings: Nanobind SID adapter

[petiaccja]

No description provided.

[petiaccja]

Depends on #1761

[petiaccja]

launch jenkins

[petiaccja]

CI failures:

• HIP node has Python 3.6.8, 3.8+ required
• tsa doesn't seem to have Python 3 development headers at all
• cray c++20: std libraries don't seem to have std::lerp which was added in c++20

[havogt]

CI failures:

* HIP node has Python 3.6.8, 3.8+ required

I'll look into updating the Python env on ault

* `tsa` doesn't seem to have Python 3 development headers at all

The mechanism for enabling Python tests is currently here https://github.com/GridTools/gridtools/blob/master/tests/regression/py_bindings/CMakeLists.txt as it's the only place were Python is used, 2 options:

• promote the Python enabling to the tests/CMakeLists.txt, or
• write a test in regression/py_bindings for nanobind
• (probably the clean solution is both: Python check at the top-level and an integration test in py_bindings)

* cray c++20: std libraries don't seem to have `std::lerp` which was added in c++20

I can try to play with the compiler versions and check if we find something that works.

[havogt]

Update on CI failures:

• ault with hip should work now
• both tsa and cray+cxx20 have Python disabled, see also CI: Daint test Cray 14.0.0 #1763 (which unfortunately doesn't work)

[petiaccja]

launch jenkins

[petiaccja]

launch jenkins

[petiaccja]

launch jenkins

[petiaccja]

launch jenkins

[petiaccja]

launch jenkins

[havogt]

let's quickly talk

[petiaccja]

launch jenkins

[petiaccja]

launch jenkins

[petiaccja]

launch jenkins

[petiaccja]

launch jenkins

[havogt]

I believe it's not needed to wrap each test in the check for GT_TESTS_ENABLE_PYTHON_TESTS as we only enable Python if was true. But there is an (unlikely?) case where it would still be needed if gridtools is added to another project with fetch_content/add_subdirectory and Python was found by this super project). So I guess we can keep it.