Skip to content

Commit f9e5e0b

Browse files
committed
pybind11 vs nanobind TLDR
1 parent 8ddb5a8 commit f9e5e0b

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

docs/why.rst

+11
Original file line numberDiff line numberDiff line change
@@ -225,3 +225,14 @@ The following lists minor-but-useful additions relative to pybind11.
225225
Please see the section on :ref:`customizing function signatures
226226
<typing_signature_functions>` and :ref:`class signatures
227227
<typing_signature_classes>` for further details.
228+
229+
TLDR
230+
----
231+
232+
My recommendation is that current pybind11 users look into migrating to
233+
nanobind. Fixing all the long-standing issues in pybind11 (see above list)
234+
would require a substantial redesign and years of careful work by a team of C++
235+
metaprogramming experts. At the same time, changing anything in pybind11 is
236+
extremely hard because of the large number of downstream users and their
237+
requirements on API/ABI stability. I personally don't have the time and
238+
energy to fix pybind11 and have moved my focus to this project.

0 commit comments

Comments
 (0)