From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] configure: Require Python 2.6
Date: Mon, 7 Sep 2015 09:49:43 +0100 [thread overview]
Message-ID: <20150907084943.GB29882@redhat.com> (raw)
In-Reply-To: <CAFEAcA9caZ8GKzFqBK7_LjHO2H9=FUwdgj7Mieuyd3s_v2SLmA@mail.gmail.com>
On Fri, Sep 04, 2015 at 11:44:17PM +0100, Peter Maydell wrote:
> On 4 September 2015 at 20:53, Markus Armbruster <armbru@redhat.com> wrote:
> > RHEL-6 and SLES-11 provide Python 2.6. It'll also work on OS X back
> > to 10.6.
> >
> > Signed-off-by: Markus Armbruster <armbru@redhat.com>
>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>
> I wonder if we're ever going to need to add that Python 3
> support the error message alludes to :-)
Possibly, but for that to be practical, we'd really need to make Python 2.7
be the min version, so Py3 is probably a good way off in the future yet.
There's no risk of Py2 dieing out any time soon so no rush :-)
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2015-09-07 8:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 19:53 [Qemu-devel] [PATCH] configure: Require Python 2.6 Markus Armbruster
2015-09-04 22:44 ` Peter Maydell
2015-09-07 8:49 ` Daniel P. Berrange [this message]
2015-09-09 17:39 ` Steve Ellcey
2015-09-09 17:43 ` Peter Maydell
2015-09-29 21:35 ` Eric Blake
2015-09-29 22:25 ` Peter Maydell
2015-10-01 11:06 ` Paolo Bonzini
2015-10-01 5:32 ` Markus Armbruster
2015-09-07 8:50 ` Daniel P. Berrange
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=20150907084943.GB29882@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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.