From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: 72432@debbugs.gnu.org
Subject: [bug#72432] [PATCH 2/2] gnu: Add python-pyclibrary.
Date: Sun, 01 Dec 2024 03:13:18 +0800 [thread overview]
Message-ID: <87ldx04jsh.wl-hako@ultrarare.space> (raw)
In-Reply-To: <20240803210441.7297-2-ngraves@ngraves.fr>
Hi Nicolas,
On Sun, 04 Aug 2024 05:04:37 +0800,
Nicolas Graves via Guix-patches via wrote:
>
> * gnu/packages/python-xyz.scm (python-pyclibrary): New variable.
>
> Change-Id: Ib4d1bf9f265fc1935c432d8e4ed3e9704f03ba70
> ---
> gnu/packages/python-xyz.scm | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
> index d09c16b73e..9dc941ca84 100644
> --- a/gnu/packages/python-xyz.scm
> +++ b/gnu/packages/python-xyz.scm
> @@ -25937,6 +25937,32 @@ (define-public python-setuptools-rust
> Rust Python extensions implemented with @code{PyO3} or @code{rust-cpython}.")
> (license license:expat)))
>
> +(define-public python-pyclibrary
> + (package
> + (name "python-pyclibrary")
> + (version "0.2.2")
> + (source
> + (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/MatthieuDartiailh/pyclibrary")
> + (commit version)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32 "0scnfk0dr8za1m7k1ml74dr8sg570sgs3hmis7fl27s2h1dbsapk"))))
> + (build-system pyproject-build-system)
> + (arguments
> + (list #:tests? #f)) ; XXX: 1/3rd of tests are failing, find out why.
Can you find out why these tests are failing? From the output it looks serious
to me.
> + (native-inputs (list python-pytest))
> + (propagated-inputs (list python-pyparsing-2.4.7))
> + (home-page "http://github.com/MatthieuDartiailh/pyclibrary")
> + (synopsis "Wrap dynamic libraries in Python")
> + (description "This package provides a library to make wrapping dynamic
> +libraries in Python less cumbersome and more user friendly. It includes a
> +pure-Python C parser and an automation library that uses C header file
> +definitions to simplify the use of C bindings.")
> + (license license:expat)))
> +
> (define-public python-pyclipper
> (package
> (name "python-pyclipper")
> --
> 2.45.2
Thanks
prev parent reply other threads:[~2024-11-30 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 23:13 [bug#72432] [PATCH 0/2] Add dlpack, python-pyclibrary Nicolas Graves via Guix-patches via
2024-08-03 21:04 ` [bug#72432] [PATCH 1/2] gnu: Add dlpack Nicolas Graves via Guix-patches via
2024-08-03 21:04 ` [bug#72432] [PATCH 2/2] gnu: Add python-pyclibrary Nicolas Graves via Guix-patches via
2024-11-30 19:13 ` Hilton Chain via Guix-patches via [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ldx04jsh.wl-hako@ultrarare.space \
--to=guix-patches@gnu.org \
--cc=72432@debbugs.gnu.org \
--cc=hako@ultrarare.space \
--cc=ngraves@ngraves.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).