From: Eduardo Habkost <ehabkost@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Fam Zheng" <famz@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
"Max Reitz" <mreitz@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v3] python: Use io.StringIO
Date: Thu, 11 Oct 2018 14:02:35 -0300 [thread overview]
Message-ID: <20181011170235.GS5738@habkost.net> (raw)
In-Reply-To: <20181011145604.GA23047@localhost.localdomain>
On Thu, Oct 11, 2018 at 04:56:04PM +0200, Kevin Wolf wrote:
> Am 11.10.2018 um 16:01 hat Markus Armbruster geschrieben:
[...]
> > I think we need to invest more resources in Python 2/3 compatiblity, or
> > else we'll miss our hard deadline of January 1, 2020.
>
> Did we decide until when we want to support Python-2-only hosts in QEMU?
>
> I think I would be okay with just getting rid of Python 2 support and
> always using Python 3 instead of trying to write code that works with
> both. Python 3 was installed for me, but the scripts didn't use it.
I'd like to drop Python 2 support on QEMU 3.1.
--
Eduardo
prev parent reply other threads:[~2018-10-11 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 21:31 [Qemu-devel] [PATCH v3] python: Use io.StringIO Philippe Mathieu-Daudé
2018-10-10 22:22 ` [Qemu-devel] [Qemu-block] " Paolo Bonzini
2018-10-11 11:33 ` [Qemu-devel] " Kevin Wolf
2018-10-11 12:43 ` [Qemu-devel] [Qemu-block] " Paolo Bonzini
2018-10-11 14:01 ` Markus Armbruster
2018-10-11 14:44 ` Philippe Mathieu-Daudé
2018-10-11 14:56 ` Kevin Wolf
2018-10-11 17:02 ` Eduardo Habkost [this message]
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=20181011170235.GS5738@habkost.net \
--to=ehabkost@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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.