From: Max Reitz <mreitz@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Cleber Rosa <crosa@redhat.com>
Cc: qemu-block@nongnu.org, "Daniel P. Berrange" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Fam Zheng" <famz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [RFC] Require Python 3 for building QEMU
Date: Sat, 13 Oct 2018 20:20:25 +0200 [thread overview]
Message-ID: <219bba9b-4102-f838-a46f-11b9704ca78f@redhat.com> (raw)
In-Reply-To: <20181013050227.17022-1-ehabkost@redhat.com>
On 13.10.18 07:02, Eduardo Habkost wrote:
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> I'd like to do this in QEMU 3.1. I think it's time to drop
> support for old systems that have only Python 2.
>
> We still have a few scripts that are not required for building
> QEMU that still work only with Python 2 (iotests being the most
> relevant set). Requiring Python 3 for building QEMU won't
> prevent people from using those scripts with Python 2 until they
> are finally ported.
It very much does because the iotests specifically use the python path
qemu was configured with.
To fix this, configure would need to write something else for into
tests/qemu-iotests/common.env for $PYTHON. But what? I don't really
want to introduce a new configure option for this.
So the real fix is indeed to make the iotests work with Python 3, and I
think that needs to be done before we can require Python 3. Maybe it
even needs to be done at the same time.
Max
> ---
> configure | 8 ++++----
> .travis.yml | 2 +-
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/configure b/configure
> index f89d293585..43b45745dc 100755
> --- a/configure
> +++ b/configure
> @@ -885,7 +885,7 @@ fi
>
> : ${make=${MAKE-make}}
> : ${install=${INSTALL-install}}
> -: ${python=${PYTHON-python}}
> +: ${python=${PYTHON-python3}}
> : ${smbd=${SMBD-/usr/sbin/smbd}}
>
> # Default objcc to clang if available, otherwise use CC
> @@ -1730,13 +1730,13 @@ exit 0
> fi
>
> if ! has $python; then
> - error_exit "Python not found. Use --python=/path/to/python"
> + error_exit "Python 3 not found. Use --python=/path/to/python"
> 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 < (2,7))'; then
> - error_exit "Cannot use '$python', Python 2 >= 2.7 or Python 3 is required." \
> +if ! $python -c 'import sys; sys.exit(sys.version_info < (3,0))'; then
> + error_exit "Cannot use '$python', Python 3 is required." \
> "Use --python=/path/to/python to specify a supported Python."
> fi
>
> diff --git a/.travis.yml b/.travis.yml
> index 95be6ec59f..caca9685fa 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -5,7 +5,7 @@ sudo: false
> dist: trusty
> language: c
> python:
> - - "2.6"
> + - "3.6"
> compiler:
> - gcc
> cache: ccache
>
next prev parent reply other threads:[~2018-10-13 18:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 5:02 [Qemu-devel] [RFC] Require Python 3 for building QEMU Eduardo Habkost
2018-10-13 14:28 ` Eric Blake
2018-10-13 18:20 ` Max Reitz [this message]
2018-10-13 20:36 ` Eduardo Habkost
2018-10-14 11:39 ` Max Reitz
2018-10-15 5:55 ` Markus Armbruster
2018-10-15 11:01 ` Max Reitz
2018-10-15 11:03 ` Max Reitz
2018-10-15 9:32 ` Daniel P. Berrangé
2018-10-15 10:02 ` Peter Maydell
2018-10-15 10:08 ` Daniel P. Berrangé
2018-10-15 10:13 ` Kevin Wolf
2018-10-15 16:33 ` Markus Armbruster
2018-10-15 16:55 ` Peter Maydell
2018-10-15 18:01 ` Eduardo Habkost
2018-10-16 3:59 ` Markus Armbruster
2018-10-16 8:14 ` Peter Maydell
2018-10-15 18:19 ` Christian Borntraeger
2018-10-15 18:33 ` Eduardo Habkost
2018-10-15 18:49 ` Christian Borntraeger
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=219bba9b-4102-f838-a46f-11b9704ca78f@redhat.com \
--to=mreitz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).