From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "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>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Deprecate Python 2 support
Date: Tue, 7 May 2019 11:47:54 +0100 [thread overview]
Message-ID: <20190507104754.GL27205@redhat.com> (raw)
In-Reply-To: <20190507103814.GF5808@localhost.localdomain>
On Tue, May 07, 2019 at 12:38:14PM +0200, Kevin Wolf wrote:
> Am 03.05.2019 um 21:37 hat Eduardo Habkost geschrieben:
> > Python 2 will reach end of life in January 1 2020. Declare it as
> > deprecated.
> >
> > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > ---
> > configure | 8 ++++++++
> > qemu-deprecated.texi | 8 ++++++++
> > 2 files changed, 16 insertions(+)
> >
> > diff --git a/configure b/configure
> > index 5b183c2e39..50385061ed 100755
> > --- a/configure
> > +++ b/configure
> > @@ -6461,6 +6461,14 @@ if test "$supported_os" = "no"; then
> > echo "us upstream at qemu-devel@nongnu.org."
> > fi
> >
> > +# Note that if the Python conditional here evaluates True we will exit
> > +# with status 1 which is a shell 'false' value.
> > +if ! $python -c 'import sys; sys.exit(sys.version_info < (3,0))'; then
> > + echo
> > + echo "WARNING: Python 2 support is deprecated" >&2
> > + echo "WARNING: Python 3 will be required for building future versions of QEMU" >&2
> > +fi
>
> While it's clear that we want to get rid of Python 2, did we actually
> discuss how to decide what the new minimum Python version is? I don't
> think any major distribution uses 3.0, which was released in 2008, so
> this doesn't seem to make a lot of sense to me as the new minimum.
>
> Currently, 3.6 seems to be a commonly available version. It looks like
> Debian stable is at 3.5 still, though it might become oldstable before
> the next QEMU release. Do we need to support anything older than that?
Per our support build platform doc, the oldest distros we care about will
be RHEL-7 and Debian Jessie. Except we can drop Jessie 2 years after
Stretch was released. IOW, we can drop Jessie in June this year, which
is before our next releasee. So we don't need to care about the 3.4
version in Jessie.
RHEL-7 doesn't have py3 at all in standard distros, but it can be obtained
via software collections and this has 3.6
Debian Strech has 3.5.3, so 3.5 looks like our min viable version.
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-05-07 10:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 19:37 [Qemu-devel] [PATCH] Deprecate Python 2 support Eduardo Habkost
2019-05-03 19:37 ` Eduardo Habkost
2019-05-04 6:27 ` Thomas Huth
2019-05-04 6:27 ` Thomas Huth
2019-05-06 14:12 ` Markus Armbruster
2019-05-07 0:53 ` Eduardo Habkost
2019-05-07 9:44 ` Daniel P. Berrangé
2019-05-07 10:38 ` Kevin Wolf
2019-05-07 10:47 ` Daniel P. Berrangé [this message]
2019-05-08 12:50 ` Markus Armbruster
2019-05-08 17:57 ` Eduardo Habkost
2019-06-06 22:28 ` 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=20190507104754.GL27205@redhat.com \
--to=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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).