From: Eduardo Habkost <ehabkost@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH] docker: move tests from python2 to python3
Date: Fri, 20 Sep 2019 18:29:12 -0300 [thread overview]
Message-ID: <20190920212912.GQ5035@habkost.net> (raw)
In-Reply-To: <20190920200049.27216-1-jsnow@redhat.com>
On Fri, Sep 20, 2019 at 04:00:49PM -0400, John Snow wrote:
> As part of the push to drop python2 support, replace any explicit python2
> dependencies with python3 versions.
>
> For centos, python2 still exists as an implicit dependency, but by adding
> python3 we will be able to build even if the configure script begins to
> require python 3.5+.
>
> Tested with centos7, fedora, ubuntu, ubuntu1804, and debian 9 (amd64).
> Tested under a custom configure script that requires Python 3.5+.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
--
Eduardo
next prev parent reply other threads:[~2019-09-20 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 20:00 [PATCH] docker: move tests from python2 to python3 John Snow
2019-09-20 21:29 ` Eduardo Habkost [this message]
2019-09-23 14:50 ` Cleber Rosa
2019-09-23 14:57 ` Philippe Mathieu-Daudé
2019-09-23 15:19 ` Cleber Rosa
2019-09-23 17:19 ` John Snow
2019-09-23 19:05 ` Debian support lifetime (was Re: [PATCH] docker: move tests from python2 to python3) Eduardo Habkost
2019-09-23 21:32 ` John Snow
2019-09-24 7:35 ` Daniel P. Berrangé
2019-09-24 9:06 ` Daniel P. Berrangé
2019-09-25 20:04 ` Eduardo Habkost
2019-09-26 11:58 ` Daniel P. Berrangé
2019-09-26 12:18 ` Peter Maydell
2019-09-26 12:44 ` Daniel P. Berrangé
2019-09-26 17:43 ` 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=20190920212912.GQ5035@habkost.net \
--to=ehabkost@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--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.