Skip to content

Commit

Permalink
pybind11 vs nanobind TLDR
Browse files Browse the repository at this point in the history
  • Loading branch information
wjakob committed Sep 9, 2024
1 parent 8ddb5a8 commit f9e5e0b
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions docs/why.rst
Original file line number Diff line number Diff line change
Expand Up @@ -225,3 +225,14 @@ The following lists minor-but-useful additions relative to pybind11.
Please see the section on :ref:`customizing function signatures
<typing_signature_functions>` and :ref:`class signatures
<typing_signature_classes>` for further details.

TLDR
----

My recommendation is that current pybind11 users look into migrating to
nanobind. Fixing all the long-standing issues in pybind11 (see above list)
would require a substantial redesign and years of careful work by a team of C++
metaprogramming experts. At the same time, changing anything in pybind11 is
extremely hard because of the large number of downstream users and their
requirements on API/ABI stability. I personally don't have the time and
energy to fix pybind11 and have moved my focus to this project.

0 comments on commit f9e5e0b

Please sign in to comment.