Contributing a guide on moving from Boost.Python to nanobind

[ManifoldFR]

Hello,

Our collision algorithms library (COAL) will soon be adding a new set of Python bindings using nanobind (see the announcement and the open PR: coal-library/coal#659)

This is the first one in our stack of robotics libraries -- next on the roadmap is the rigid-body dynamics library Pinocchio, and more downstream libraries handling stuff like simulation, optimization and MPC.

We had never moved to pybind11 back in the day, but we've finally made the choice to move to nanobind, because Boost.Python is a huge drag to work with and is practically dead. nanobind is really really good (the recent additions like nb::def_visitor also helped along the transition).

Once we are done, we could contribute a small guide to nanobind's docs on how to move from Boost.Python to nanobind. We could perhaps add a few benchmarks from COAL (old Boost.Python bindings vs. nanobind). Would that be interesting?

[wjakob]

Sounds lovely!