I would be open to it but have my doubts about the feasibility of a merge. Consider the difference in code size alone: Boost.Python (without dependencies like MPL etc.) uses 26K lines of code, compared to about 2K for pybind11 (3K with all extensions). Apart from that, the libraries take very different internal design decisions, which would likely break existing software that ventures beyond the basic .def() syntax.
Cheers, Wenzel > On Oct 19, 2015, at 11:24 AM, Trigve Siver via Cplusplus-sig > <cplusplus-sig@python.org> wrote: > >> ________________________________ >> From: Wenzel Jakob <wen...@inf.ethz.ch> >> To: cplusplus-sig@python.org >> Sent: Sunday, October 18, 2015 2:56 PM >> Subject: [C++-sig] pybind11 -- alternative to Boost.Python >> > It looks good. > Have you tried contacting the actual boost.python mantainer and maybe propose > merge with the boost.python or make a boost.python3 from it? It would be > shame not incorporate the useful stuff in boost.python. >
_______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org https://mail.python.org/mailman/listinfo/cplusplus-sig
