From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: Require python3 >= 3.5
Date: Thu, 9 May 2019 11:24:25 +0200 [thread overview]
Message-ID: <20190509092425.GB6850@localhost.localdomain> (raw)
In-Reply-To: <87ftpo89le.fsf@dusky.pond.sub.org>
Am 09.05.2019 um 07:45 hat Markus Armbruster geschrieben:
> Eduardo Habkost <ehabkost@redhat.com> writes:
> > diff --git a/.travis.yml b/.travis.yml
> > index 66448d99d6..0f6986b3f1 100644
> > --- a/.travis.yml
> > +++ b/.travis.yml
> > @@ -211,7 +211,7 @@ matrix:
> > - CONFIG="--target-list=x86_64-softmmu"
> > language: python
> > python:
> > - - "3.4"
> > + - "3.5"
> >
> >
> > - env:
>
> Easily missed, good work.
>
> My grep for similar references to Python versions we don't support found
> a few 2.x, x < 7. Not this patch's problem, of course, but let me show
> them anyway:
I'm sure that we have a few more instances of Python 2 compatibility
code in qemu-iotests that can be removed after this is merged. These are
what I could find quickly, but there are probably more:
242: # Read one byte in a way compatible with Python 2
iotests.py: # Python < 3.4 needs to know not to add whitespace when pretty-printing:
149:from __future__ import print_function
165:from __future__ import print_function
iotests.py:from __future__ import print_function
nbd-fault-injector.py:from __future__ import print_function
qcow2.py:from __future__ import print_function
qed.py:from __future__ import print_function
044:if sys.version_info.major == 2:
163:if sys.version_info.major == 2:
iotests.py: if sys.version_info.major >= 3:
iotests.py: if sys.version_info.major >= 3:
nbd-fault-injector.py:if sys.version_info.major >= 3:
I'm planning to take care of the qemu-iotests ones.
Also, with Python 3.5 as the new minimum, I think I'd like to add type
hints to iotests.py and possibly the qemu package (for QEMUQtestMachine
and friends). The syntax isn't as nice as if we could go straight to
3.6, but still, finally some type checking instead of running into
stupid runtime bugs!
Kevin
next prev parent reply other threads:[~2019-05-09 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 18:23 [Qemu-devel] [PATCH] configure: Require python3 >= 3.5 Eduardo Habkost
2019-05-09 5:40 ` Thomas Huth
2019-05-09 5:45 ` Markus Armbruster
2019-05-09 9:24 ` Kevin Wolf [this message]
2019-05-09 9:36 ` Kevin Wolf
2019-05-09 9:40 ` Daniel P. Berrangé
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=20190509092425.GB6850@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).