GNU bug report logs - #55084
[PATCH] gnu: python-numpy-next: Update to 1.22.3.

Previous Next

Package: guix-patches;

Reported by: Felix Gruber <felgru <at> posteo.net>

Date: Sat, 23 Apr 2022 16:49:02 UTC

Severity: normal

Tags: patch

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: zimoun <zimon.toutoune <at> gmail.com>
To: Mathieu Othacehe <othacehe <at> gnu.org>
Cc: Felix Gruber <felgru <at> posteo.net>, 55084 <at> debbugs.gnu.org
Subject: [bug#55084] [PATCH] gnu: python-numpy-next: Update to 1.22.3.
Date: Tue, 26 Apr 2022 12:59:33 +0200
Hi Mathieu,

On Tue, 26 Apr 2022 at 11:23, Mathieu Othacehe <othacehe <at> gnu.org> wrote:

> > +    (native-inputs
> > +     (list python-cython python-hypothesis python-pytest
> > +           python-pytest-xdist gfortran))
>
> What about using something like:
>
> --8<---------------cut here---------------start------------->8---
>     (native-inputs
>      (modify-inputs (package-inputs python-numpy-next)
>        (delete "python-hypothesis")
>        (prepend python-hypothesis)))
> --8<---------------cut here---------------end--------------->8---
>
> not to duplicate the native-inputs list?

I do not think it is possible because, whereas this 'modify-inputs' is
better for readibility, it implies a rebuild of the package, IMHO; the
very thing we would like to avoid since touching to python-numpy is a
core-update modification.

However, maybe python-numpy-next could inherit from python-numpy
instead of the contrary.  Well, I do not know if it is better...


Cheers,
simon




This bug report was last modified 3 years and 10 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.