[bug#31431] [PATCH 0/1] gnu: Add pybind11.

[bug#31431] [PATCH 0/1] gnu: Add pybind11.

[Fis Trivial]

pybind11 is a c++ library for python binding. I don't know if it's
appropriate to put it in python.scm. I checked libffi, libffcall, swig,
they all have their independent file, and all of them contains very few
packages.

Should I merge them into one file just named "ffi.scm"?

fis (1):
  gnu: Add pybind11.

 gnu/packages/python.scm | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

-- 
2.14.3

[bug#31431] [PATCH 1/1] gnu: Add pybind11.

[Fis Trivial]

* gnu/packages/python.scm (pybind11): New variable.
---
 gnu/packages/python.scm | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index f942a2be4..b0099d354 100644
--- a/gnu/packages/python.scm
+++ b/gnu/packages/python.scm
@@ -13297,3 +13297,31 @@ generators and Python 3.7's context managers into Python 3.5.")
 manager compatible with @code{asyncio}.")
     (license license:asl2.0)))
 
+(define-public pybind11
+  (package
+    (name "pybind11")
+    (version "2.2.3")
+    (source (origin
+              (method url-fetch)
+              (uri (string-append
+                    "https://github.com/pybind/pybind11/archive/v"
+                    version ".tar.gz"))
+              (sha256
+               (base32
+                "1sj0x4fwsbnwdai5sxpw1l1vh8m5hpbkfk3zanxcbcgs39jpnfrs"))
+              (file-name (string-append name "-" version ".tar.gz"))))
+    (build-system cmake-build-system)
+    (native-inputs
+     `(("python" ,python)
+       ("python-pytest" ,python-pytest)))
+    (arguments
+     `(#:test-target "check"))
+    (home-page "https://github.com/pybind/pybind11/")
+    (synopsis "Seamless operability between C++11 and Python")
+    (description "pybind11 is a lightweight header-only library that exposes
+C++ types in Python and vice versa, mainly to create Python bindings of
+existing C++ code.  Its goals and syntax are similar to the excellent
+Boost.Python library by David Abrahams: to minimize boilerplate code in
+traditional extension modules by inferring type information using compile-time
+introspection.")
+    (license license:expat)))
-- 
2.14.3

bug#31431: [PATCH 0/1] gnu: Add pybind11.

[Ludovic Courtès]

Hello,

Fis Trivial <ybbs.daans@hotmail.com> skribis:

> pybind11 is a c++ library for python binding. I don't know if it's
> appropriate to put it in python.scm. I checked libffi, libffcall, swig,
> they all have their independent file, and all of them contains very few
> packages.
>
> Should I merge them into one file just named "ffi.scm"?

I’ve now applied the patch as-is, but moving all these things to ffi.scm
would make sense, yes.

Thank you,
Ludo’.