unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Antero Mejr <antero@mailbox.org>
Cc: lars@6xq.net, 59792@debbugs.gnu.org
Subject: [bug#59792] [PATCH] gnu: Add python-pynetdicom.
Date: Mon, 16 Jan 2023 09:50:10 -0500	[thread overview]
Message-ID: <87lem2a5zx.fsf_-_@gmail.com> (raw)
In-Reply-To: <20221203050829.30666-1-antero@mailbox.org> (Antero Mejr's message of "Sat, 3 Dec 2022 05:08:29 +0000")

Hello Antero!

Antero Mejr <antero@mailbox.org> writes:

> * gnu/packages/python-science.scm (python-pydicom): New variable.

Thanks for this contribution.

> Please apply this patch first.
> Supersedes #55989.
>
>  gnu/packages/python-science.scm | 46 +++++++++++++++++++++++++++++++++
>  1 file changed, 46 insertions(+)
>
> diff --git a/gnu/packages/python-science.scm b/gnu/packages/python-science.scm
> index 52fe1460bb..00bba25a4a 100644
> --- a/gnu/packages/python-science.scm
> +++ b/gnu/packages/python-science.scm
> @@ -1656,6 +1656,52 @@ (define-public python-vaex-core
>  tabular datasets.  This package provides the core modules of Vaex.")
>      (license license:expat)))
>  
> +(define-public python-pydicom
> +  (package
> +    (name "python-pydicom")
> +    (version "2.3.1")
> +    (source (origin
> +              (method git-fetch)
> +              (uri (git-reference
> +                    (url "https://github.com/pydicom/pydicom")
> +                    (commit (string-append "v" version))))
> +              (file-name (git-file-name name version))
> +              (sha256
> +               (base32
> +                "0q209i2jgwv5z1xhi7frydkplby7jaiz624pjq6vi51wvlmimpf6"))))
> +    (build-system python-build-system)
> +    (arguments
> +     (list #:phases #~(modify-phases %standard-phases
> +                        (replace 'check
> +                          (lambda* (#:key tests? #:allow-other-keys)
> +                            (when tests?
> +                              ;; skip tests using external data

Well done!  Please use a complete sentence for stand-alone comments,
e.g. ";; Skip tests that require networking."

> +                              (invoke "pytest" "-vv" "-k"
> +                                      (string-append
> +                                       " not TestDataElement"
> +                                       " and not TestDatasetOverlayArray"
> +                                       " and not TestReader"
> +                                       " and not Test_JPEG_LS_Lossless_transfer_syntax"
> +                                       " and not test_data_manager.py"
> +                                       " and not test_encaps.py"
> +                                       " and not test_encoders_pydicom.py"
> +                                       " and not test_filewriter.py"
> +                                       " and not test_gdcm_pixel_data.py"
> +                                       " and not test_handler_util.py"
> +                                       " and not test_jpeg_ls_pixel_data.py"
> +                                       " and not test_numpy_pixel_data.py"
> +                                       " and not test_overlay_np.py"
> +                                       " and not test_pillow_pixel_data.py"
> +                                       " and not test_rle_pixel_data.py"))))))))

Suggestion: If you use pyproject-build-system, you can avoid overriding
the test phase, instead making use of the new #:test-flags argument, to
provide just the "-k" and patterns.

> +    (native-inputs (list python-pytest))
> +    (propagated-inputs (list python-numpy python-pillow))
> +    (home-page "https://github.com/pydicom/pydicom")
> +    (synopsis "Python library for reading and writing DICOM data")
> +    (description "@code{pydicom} is a Python library for reading and writing
> +DICOM medical image files.  It lets developers read, modify and write DICOM data
> +in a pythonic way.")

I'd avoid "developers", and plainly state: "It can read, modify [...]",
and drop "in a pythonic way" since that's more subjective than facts.

-- 
Thanks,
Maxim




  reply	other threads:[~2023-01-16 14:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03  5:03 [bug#59792] [PATCH] gnu: Add python-pynetdicom Antero Mejr via Guix-patches via
2022-12-03  5:08 ` [bug#59792] [PATCH] gnu: Add python-pydicom Antero Mejr via Guix-patches via
2023-01-16 14:50   ` Maxim Cournoyer [this message]
2023-01-16 14:53 ` [bug#59792] [PATCH] gnu: Add python-pynetdicom Maxim Cournoyer
2024-01-24  0:18 ` bug#59792: " Sharlatan Hellseher

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=87lem2a5zx.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=59792@debbugs.gnu.org \
    --cc=antero@mailbox.org \
    --cc=lars@6xq.net \
    /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).