From: Efraim Flashner <efraim@flashner.co.il>
To: zimoun <zimon.toutoune@gmail.com>
Cc: BonfaceKilz <me@bonfacemunyoki.com>, 47183@debbugs.gnu.org
Subject: [bug#47183] [PATCH 0/1] *** Numpy Update to v1.20.1 ***
Date: Tue, 16 Mar 2021 15:27:31 +0200 [thread overview]
Message-ID: <YFCyQ5ZueV2+z4bx@3900XT> (raw)
In-Reply-To: <CAJ3okZ2iOanR5P2CyEN_aM4JG9pvVU95-YfyydRSHTjLEHG4MQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
On Tue, Mar 16, 2021 at 02:18:56PM +0100, zimoun wrote:
> Hi,
>
> 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.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-16 13:29 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 [this message]
2021-03-16 18:35 ` Bonface Munyoki K.
2021-06-10 8:36 ` zimoun
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YFCyQ5ZueV2+z4bx@3900XT \
--to=efraim@flashner.co.il \
--cc=47183@debbugs.gnu.org \
--cc=me@bonfacemunyoki.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.