From: Antero Mejr via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 55989@debbugs.gnu.org
Subject: [bug#55989] [PATCH 1/2] gnu: Add python-pydicom.
Date: Wed, 15 Jun 2022 15:40:52 +0000 [thread overview]
Message-ID: <87bkuuc4n3.fsf@mailbox.org> (raw)
In-Reply-To: <791d27fa1be5e3c0c2410fbe823c63b73f85a19e.camel@telenet.be>
Maxime Devos <maximedevos@telenet.be> writes:
> 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?
Sure, see updated patch. I looked through the error log to confirm
that the tests were failing due to missing data. I also did an
end-to-end test of pydicom by importing it, then reading/writing
a DICOM file.
>
>> + (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.
>
OK, updated.
>> + 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}.
>
Updated.
next prev parent reply other threads:[~2022-06-15 15:47 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 ` [bug#55989] [PATCH 1/2] gnu: Add python-pydicom Maxime Devos
2022-06-15 15:40 ` Antero Mejr via Guix-patches via [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkuuc4n3.fsf@mailbox.org \
--to=guix-patches@gnu.org \
--cc=55989@debbugs.gnu.org \
--cc=antero@mailbox.org \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.