From: Maxime Devos <maximedevos@telenet.be>
To: Antero Mejr <antero@mailbox.org>, 55989@debbugs.gnu.org
Subject: [bug#55989] [PATCH 1/2] gnu: Add python-pydicom.
Date: Wed, 15 Jun 2022 09:59:56 +0200 [thread overview]
Message-ID: <791d27fa1be5e3c0c2410fbe823c63b73f85a19e.camel@telenet.be> (raw)
In-Reply-To: <20220615012714.1414-1-antero@mailbox.org>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
Antero Mejr via Guix-patches via schreef op wo 15-06-2022 om 01:27
[+0000]:
> + ;; 181 failed, 2235 pass. Pulls test datasets off the web, no-go for Guix
> + #:tests? #f
How about only disabling tests that download from the web?
Are all of these test failures due to downloading from the web or are
there some other tests too?
> + (synopsis "Pure Python package for reading and writing DICOM data")
Unlike some language-specific package managers, Guix supports using dependents
from other languages without any complications, so no need to mention ‘Pure’
here.
> + pydicom provides a pure Python package
It doesn't provide a Python package, it is a Python package, especially if pydicom
is replaced by @code{python-pydicom}.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-15 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 1:27 [bug#55989] [PATCH 1/2] gnu: Add python-pydicom Antero Mejr via Guix-patches via
2022-06-15 1:27 ` [bug#55988] [PATCH 2/2] gnu: Add gdcm Antero Mejr via Guix-patches via
2022-06-15 7:59 ` Maxime Devos [this message]
2022-06-15 15:40 ` [bug#55989] [PATCH 1/2] gnu: Add python-pydicom Antero Mejr via Guix-patches via
2022-06-15 15:39 ` Antero Mejr via Guix-patches via
2022-06-15 15:39 ` [bug#55989] [PATCH 2/2] gnu: Add gdcm Antero Mejr via Guix-patches via
2023-01-08 15:06 ` bug#55989: [PATCH 1/2] gnu: Add python-pydicom Ludovic Courtès
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=791d27fa1be5e3c0c2410fbe823c63b73f85a19e.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55989@debbugs.gnu.org \
--cc=antero@mailbox.org \
/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).