From: zimoun <zimon.toutoune@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: Felix Gruber <felgru@posteo.net>, 55084@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 [thread overview]
Message-ID: <CAJ3okZ1CnY397Nu6gNLfyQztV_ZZhgQfF_NA6D8m5ZSw2Cg39w@mail.gmail.com> (raw)
In-Reply-To: <87r15kurlc.fsf@gnu.org>
Hi Mathieu,
On Tue, 26 Apr 2022 at 11:23, Mathieu Othacehe <othacehe@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
next prev parent reply other threads:[~2022-04-26 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 16:48 [bug#55084] [PATCH] gnu: python-numpy-next: Update to 1.22.3 Felix Gruber
2022-04-26 9:22 ` Mathieu Othacehe
2022-04-26 10:59 ` zimoun [this message]
2022-05-09 10:26 ` bug#55084: " 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=CAJ3okZ1CnY397Nu6gNLfyQztV_ZZhgQfF_NA6D8m5ZSw2Cg39w@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=55084@debbugs.gnu.org \
--cc=felgru@posteo.net \
--cc=othacehe@gnu.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).