You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have the long term goal of removing the dependency on Boost.Python, and the current strategy is to rewrite the bindings with pybind11, although nanobind promises to be even better than pybind11, and also claims to be largely API-compatible.
We should prototype bindings using nanobind. This would involve duplicating the current state of the pybind11 bindings, both source and CMake configuration, and replacing both to use nanobind.
The text was updated successfully, but these errors were encountered:
We have the long term goal of removing the dependency on Boost.Python, and the current strategy is to rewrite the bindings with pybind11, although nanobind promises to be even better than pybind11, and also claims to be largely API-compatible.
We should prototype bindings using nanobind. This would involve duplicating the current state of the pybind11 bindings, both source and CMake configuration, and replacing both to use nanobind.
The text was updated successfully, but these errors were encountered: