All of lore.kernel.org
 help / color / mirror / Atom feed
From: joannah nanjekye <nanjekyejoannah@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
	qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH WIP] replace numpy with struct
Date: Fri, 3 Nov 2017 15:34:46 +0300	[thread overview]
Message-ID: <CANFMCgQf4gE4Tsm0uPfq4ADD2TrinjpazTzp4Yh3+4d2wwr3vw@mail.gmail.com> (raw)
In-Reply-To: <20171103112442.GN5078@stefanha-x1.localdomain>

I will send an update tomorrow as am travelling rite now.

Thanks for the reminder.

On Nov 3, 2017 2:24 PM, "Stefan Hajnoczi" <stefanha@gmail.com> wrote:

> On Thu, Oct 26, 2017 at 10:50:26AM -0300, Philippe Mathieu-Daudé wrote:
> > Hi Joannah,
> >
> > The common subject to use is [RFC PATCH] instead of [PATCH WIP]
> >
> > On 10/26/2017 09:14 AM, Joannah Nanjekye wrote:
> > > This patch replaces the use of numpy with the standard Library struct
> module where possible.
> >
> > This seems a good idea but why?
>
> I suggest adding this to the commit description:
>
> Users tend to hit an ImportError when running analyze-migration.py due
> to the numpy dependency.  numpy functionality isn't actually used, just
> binary serialization that the standard library 'struct' module already
> provides.  Removing the dependency allows the script to run
> out-of-the-box.
>
> > Do you have any performance improvements results to share?
> >
> > > Signed-off-by: Joannah Nanjekye <nanjekyejoannah@gmail.com>
> > > ---
> > >
> > >  scripts/analyze-migration.py | 19 ++++++++++++-------
> > >  1 file changed, 12 insertions(+), 7 deletions(-)
>
> I don't see a removal of "import numpy as np" so this script still
> depends on numpy.  Did you forget to sent further patches that you have
> to remove the numpy dependency?
>

  reply	other threads:[~2017-11-03 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 12:14 [Qemu-devel] [PATCH WIP] replace numpy with struct Joannah Nanjekye
2017-10-26 13:50 ` Philippe Mathieu-Daudé
2017-11-03 11:24   ` Stefan Hajnoczi
2017-11-03 12:34     ` joannah nanjekye [this message]
2017-11-03 13:10     ` Philippe Mathieu-Daudé

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=CANFMCgQf4gE4Tsm0uPfq4ADD2TrinjpazTzp4Yh3+4d2wwr3vw@mail.gmail.com \
    --to=nanjekyejoannah@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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.
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.