GNU bug report logs - #31431
[PATCH 0/1] gnu: Add pybind11.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 31431 in the body.
You can then email your comments to 31431 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Fis Trivial <ybbs.daans <at> hotmail.com>
To: "guix-patches <at> gnu.org" <guix-patches <at> gnu.org>
Subject: [PATCH 0/1] gnu: Add pybind11.
Date: Sat, 12 May 2018 14:51:30 +0000

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

Message #8 received at 31431 <at> debbugs.gnu.org (full text, mbox):

From: Fis Trivial <ybbs.daans <at> hotmail.com>
To: "31431 <at> debbugs.gnu.org" <31431 <at> debbugs.gnu.org>
Subject: [PATCH 1/1] gnu: Add pybind11.
Date: Sat, 12 May 2018 14:53:56 +0000

* 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

Message #13 received at 31431-done <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Fis Trivial <ybbs.daans <at> hotmail.com>
Cc: 31431-done <at> debbugs.gnu.org
Subject: Re: [bug#31431] [PATCH 0/1] gnu: Add pybind11.
Date: Sat, 26 May 2018 22:51:02 +0200

Hello,

Fis Trivial <ybbs.daans <at> 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’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.