From: jgart via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 55896@debbugs.gnu.org
Subject: [bug#55896] [PATCH v2] gnu: Add python-pybare.
Date: Sun, 12 Jun 2022 15:54:18 -0500 [thread overview]
Message-ID: <20220612155418.GC1648@gac> (raw)
In-Reply-To: <fa829031dd0a11841914052a5277b3852e99db82.camel@telenet.be>
On Sun, 12 Jun 2022 17:41:57 +0200 Maxime Devos <maximedevos@telenet.be> wrote:
> jgart schreef op za 11-06-2022 om 15:27 [-0500]:
> > +(define-public python-pybare
> > + (package
> > + (name "python-pybare")
> > + (version "0.1.1")
> > + (source
> > + (origin
> > + (method git-fetch)
> > + (uri
> > + (git-reference
> > + (url "https://git.sr.ht/~chiefnoah/pybare")
> > + (commit (string-append "v" version))))
> > + (file-name (git-file-name name version))
> > + (sha256
> > + (base32 "1ibmwwf1rdxlwyxlzhv3v1i0ybsqg0kppim90sm8rsbns86yy4by"))))
> > + (build-system python-build-system)
> > + (arguments
> > + (list #:phases
> > + #~(modify-phases %standard-phases
> > + (replace 'check
> > + (lambda* (#:key tests? #:allow-other-keys)
> > + (when tests?
> > + (chdir "bare")
> > + (invoke "pytest" "-vv" ".")))))))
> > + (native-inputs
> > + (list python-pytest))
> > + (home-page "https://sr.ht/~chiefnoah/PyBARE/")
> > + (synopsis "Declarative implementation of BARE for Python")
> > + (description
> > +"@code{python-pybare} is a general purpose library for strongly typed
> > +primitives in Python that supports serializing to and from @acronym{BARE,
> > +Binary Application Record Encoding} messages.")
> > + (license license:expat
>
>
> Package definition LGTM, but I have only looked at the definition, not
> the sources etc.
Hi Maxime, no worries. Take your time. The review is much appreciated.
I just looked at the sources again myself and noticed that the tests
use pre-generated BARE binaries to test against.
See here:
https://git.sr.ht/~chiefnoah/pybare/tree/master/item/bare/test_encoder.py#L225
and here:
https://git.sr.ht/~chiefnoah/pybare/tree/master/item/bare/_examples
Should I ask the author if they can provide a way to generate those
binaries for testing instead of vendoring the pre-compiled binaries
without their sources?
all best,
jgart
next prev parent reply other threads:[~2022-06-12 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 4:27 [bug#55896] [PATCH] gnu: Add python-pybare jgart via Guix-patches via
2022-06-11 8:21 ` Maxime Devos
2022-06-11 20:27 ` [bug#55896] [PATCH v2] " jgart via Guix-patches via
2022-06-12 15:41 ` Maxime Devos
2022-06-12 20:54 ` jgart via Guix-patches via [this message]
2022-07-07 20:33 ` [bug#55896] [PATCH] " Maxim Cournoyer
2022-07-07 23:59 ` jgart via Guix-patches via
2024-06-18 6:07 ` bug#55896: jgart via Guix-patches via
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=20220612155418.GC1648@gac \
--to=guix-patches@gnu.org \
--cc=55896@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=maximedevos@telenet.be \
/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).