From: "Daniel P. Berrangé" <berrange@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
qemu-devel@nongnu.org, Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH] configure: Require Python >= 3.5
Date: Thu, 17 Oct 2019 09:55:30 +0100 [thread overview]
Message-ID: <20191017085530.GD31072@redhat.com> (raw)
In-Reply-To: <7146bebf-6e99-f27a-3753-d48dea1977f9@redhat.com>
On Wed, Oct 16, 2019 at 06:48:34PM -0400, John Snow wrote:
>
>
> On 10/16/19 6:42 PM, Eduardo Habkost wrote:
> > Python 3.5 is the oldest Python version available on our
> > supported build platforms, and Python 2 end of life will be 3
> > weeks after the planned release date of QEMU 4.2.0. Drop Python
> > 2 support from configure completely, and require Python 3.5 or
> > newer.
> >
> > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
>
> Seems like a good time and place to mention this. Kevin, you require
> 3.6+ for iotests, which are -- at present -- invoked as part of "make
> check".
>
> Do we care? Basically, this just means that iotests won't run for
> systems that don't have 3.6+, which would be platforms like Debian 9 --
> which is why ehabkost is choosing 3.5 here.
Depends what the reason for pickin 3.6 was ? Is it really compelling
for iotests to require 3.6, or is it easy to support 3.5. I think in
general it is desirable to have a consistent story across the codebase
for min versions
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:[~2019-10-17 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 22:42 [PATCH] configure: Require Python >= 3.5 Eduardo Habkost
2019-10-16 22:48 ` John Snow
2019-10-17 7:56 ` Thomas Huth
2019-10-17 8:55 ` Daniel P. Berrangé [this message]
2019-10-17 11:21 ` Kevin Wolf
2019-10-17 19:39 ` John Snow
2019-10-18 8:15 ` Kevin Wolf
2019-10-18 21:05 ` John Snow
2019-10-18 21:07 ` John Snow
2019-10-18 21:14 ` Eduardo Habkost
2019-10-18 21:18 ` John Snow
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=20191017085530.GD31072@redhat.com \
--to=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).