From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 52906@debbugs.gnu.org
Subject: bug#52906: python-biopython conflicts with python-numpy
Date: Fri, 31 Dec 2021 13:43:13 +0100 [thread overview]
Message-ID: <87y241eyg5.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ2frU0RJRjxWs9XtOBmS5-4TiA-3N1rjKVYCi1n+ONAEA@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> Hi Ricardo,
>
> On Fri, 31 Dec 2021 at 11:18, Ricardo Wurmus <rekado@elephly.net> wrote:
>> zimoun <zimon.toutoune@gmail.com> writes:
>
>> Back then we reverted to numpy 1.20.x as the default because of numba,
>> which did not work with 1.21. I’m now upgrading numba (and llvmlite) to
>> a more recent release candidate, which should bring compatibility with
>> numpy 1.21.
>>
>> If that works we’ll make python-numpy-next the new python-numpy.
>
> I think that it could nice to have "python-numpy-next". Now, because
> we are right after a core-updates, the last Numpy version and the one
> we use as scientific Python stack are really close. But it will not
> necessary the case between 2 core-updates merges. Well, my point is
> to have the core-updates package python-numpy used by all the
> scientific Python stack and the leaf package python-numpy-next where
> updates can happen on master, it can be used with transformations
> etc., especially by scientific Python developper.
Yes, it’s a good idea to have it anyway.
I just realized that switching over to the new numpy is going to cause
more than a 1000 rebuilds. So I’ll apply your patch on the master
branch and build out the numpy upgrade on a separate branch.
Thank you!
--
Ricardo
next prev parent reply other threads:[~2021-12-31 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 21:13 bug#52906: python-biopython conflicts with python-numpy zimoun
2021-12-30 23:55 ` Leo Famulari
2021-12-31 10:14 ` Ricardo Wurmus
2021-12-31 10:51 ` zimoun
2021-12-31 12:43 ` Ricardo Wurmus [this message]
2021-12-31 13:16 ` zimoun
2021-12-31 20:18 ` Ricardo Wurmus
2021-12-31 12:50 ` Ricardo Wurmus
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=87y241eyg5.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=52906@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).