From: zimoun <zimon.toutoune@gmail.com>
To: Bonface Munyoki K. <me@bonfacemunyoki.com>
Cc: 47183@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#47183] [PATCH 0/1] *** Numpy Update to v1.20.1 ***
Date: Thu, 10 Jun 2021 10:36:30 +0200 [thread overview]
Message-ID: <864ke6ktf5.fsf@gmail.com> (raw)
In-Reply-To: <86h7lbt09w.fsf@bonfacemunyoki.com> (Bonface Munyoki K.'s message of "Tue, 16 Mar 2021 21:35:07 +0300")
Hi,
On Tue, 16 Mar 2021 at 21:35, Bonface Munyoki K. <me@bonfacemunyoki.com> wrote:
> Efraim Flashner <efraim@flashner.co.il> writes:
>> On Tue, Mar 16, 2021 at 02:18:56PM +0100, zimoun wrote:
>>> On Tue, 16 Mar 2021 at 09:01, BonfaceKilz <me@bonfacemunyoki.com> wrote:
>>>
>>> > Hi all! This patche updates python-numpy to v1.20.1 from 1.17.3. This
>>> > update
>>> > is important since numpy has introduced type annotations which is very
>>> > useful
>>> > for CI when using a type checking tool such as mypy.
>>>
>>> I have not tried this one, but I have tried 1.19.4
>>> <http://issues.guix.gnu.org/issue/45698> and I got some failure with
>>> some dependants of Numpy. Have you checked that the update does not
>>> break other packages?
>>>
>> I found that matplotlib and scipy both had test failures.
>
> Let me look into this and supply patches
> accordingly!
I propose to close this one in favor of patch#48703. WDYT?
Cheers,
simon
<http://issues.guix.gnu.org/issue/48703>
next prev parent reply other threads:[~2021-06-10 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 8:00 [bug#47183] [PATCH 0/1] *** Numpy Update to v1.20.1 *** BonfaceKilz
2021-03-16 8:00 ` [bug#47184] [PATCH 1/1] gnu: python-numpy: Update to 1.20.1 BonfaceKilz
2021-03-16 13:18 ` [bug#47183] [PATCH 0/1] *** Numpy Update to v1.20.1 *** zimoun
2021-03-16 13:27 ` Efraim Flashner
2021-03-16 18:35 ` Bonface Munyoki K.
2021-06-10 8:36 ` zimoun [this message]
2021-06-14 6:54 ` Bonface Munyoki K.
2021-06-16 5:34 ` bug#47183: " zimoun
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=864ke6ktf5.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=47183@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=me@bonfacemunyoki.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).