From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: Require Python 2.7 or newer
Date: Fri, 8 Jun 2018 16:07:46 +0100 [thread overview]
Message-ID: <20180608150746.GX18233@redhat.com> (raw)
In-Reply-To: <20180608145559.GI7451@localhost.localdomain>
On Fri, Jun 08, 2018 at 11:55:59AM -0300, Eduardo Habkost wrote:
> On Fri, Jun 08, 2018 at 03:37:47PM +0100, Daniel P. Berrangé wrote:
> > On Fri, Jun 08, 2018 at 11:30:26AM -0300, Eduardo Habkost wrote:
> > > All of the supported build platforms documented in qemu-doc.texi
> > > should already support Python 2.7.
> > >
> > > Removing support for Python 2.6 will allow us to remove some
> > > compatibility modules we carry in the QEMU tree:
> > >
> > > * scripts/argparse.py
> > > * scripts/ordereddict.py
> >
> > Lets delete those in this patch then....
>
> I will do it, but I prefer to do this in a separate patch.
Ok that's fine
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-06-08 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 14:30 [Qemu-devel] [PATCH] configure: Require Python 2.7 or newer Eduardo Habkost
2018-06-08 14:37 ` Philippe Mathieu-Daudé
2018-06-08 14:40 ` Daniel P. Berrangé
2018-06-08 14:59 ` Philippe Mathieu-Daudé
2018-06-08 14:37 ` Daniel P. Berrangé
2018-06-08 14:55 ` Eduardo Habkost
2018-06-08 15:07 ` Daniel P. Berrangé [this message]
2018-06-08 15:03 ` Eduardo Habkost
2018-06-08 15:07 ` Daniel P. Berrangé
2018-06-08 16:14 ` Cleber Rosa
2018-06-08 19:19 ` John Snow
2018-06-11 13:52 ` Stefan Hajnoczi
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=20180608150746.GX18233@redhat.com \
--to=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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 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 NNTP newsgroup(s).