From: Juan Quintela <quintela@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"John Snow" <jsnow@redhat.com>, "Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [PULL 2/2] configure: Require Python >= 3.5
Date: Fri, 20 Dec 2019 19:59:28 +0100 [thread overview]
Message-ID: <8736deakmn.fsf@trasno.org> (raw)
In-Reply-To: <20191220165141.2207058-3-ehabkost@redhat.com> (Eduardo Habkost's message of "Fri, 20 Dec 2019 13:51:41 -0300")
Eduardo Habkost <ehabkost@redhat.com> 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>
> Message-Id: <20191016224237.26180-1-ehabkost@redhat.com>
> Reviewed-by: John Snow <jsnow@redhat.com>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
But once here, a comment telling why we want 3.5, not 3.4 or 3.6 will
have been helpful.
Later, Juan.
next prev parent reply other threads:[~2019-12-20 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 16:51 [PULL 0/2] Require Python >= 3.5 to build QEMU Eduardo Habkost
2019-12-20 16:51 ` [PULL 1/2] travis: Replace Python 3.4 build with 3.5 Eduardo Habkost
2019-12-20 16:51 ` [PULL 2/2] configure: Require Python >= 3.5 Eduardo Habkost
2019-12-20 18:59 ` Juan Quintela [this message]
2019-12-20 20:12 ` Eduardo Habkost
2019-12-23 10:24 ` Juan Quintela
2019-12-20 16:53 ` [PULL 0/2] Require Python >= 3.5 to build QEMU Philippe Mathieu-Daudé
2020-01-06 14:07 ` Peter Maydell
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=8736deakmn.fsf@trasno.org \
--to=quintela@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--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.