From: Markus Armbruster <armbru@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Can we retire Python 2 now?
Date: Sat, 21 Dec 2019 08:59:09 +0100 [thread overview]
Message-ID: <87tv5up0s2.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20191220165627.GV498046@habkost.net> (Eduardo Habkost's message of "Fri, 20 Dec 2019 13:56:27 -0300")
Eduardo Habkost <ehabkost@redhat.com> writes:
> On Fri, Dec 20, 2019 at 05:29:30PM +0100, Markus Armbruster wrote:
>> Python 2 EOL is only a few days away[*]. We made configure bitch about
>> it in commit e5abf59eae "Deprecate Python 2 support", 2019-07-01. Any
>> objections to retiring it now, i.e. in 5.0?
>
> Thanks for the reminder!
>
> I'll be honest: even if somebody in this list objects to dropping
> Python 2 support, I'm not willing to be maintainer of a Python 2
> codebase in 2020. The only reason for not doing it in 4.1 was
> the tests/vm/netbsd breakage we took very long to debug and fix.
I wasn't exactly "willing" in 2019...
> I have just submitted this pull request:
>
> Subject: [PULL 0/2] Require Python >= 3.5 to build QEMU
> https://lore.kernel.org/qemu-devel/20191220165141.2207058-1-ehabkost@redhat.com/
Awesome, thanks!
next prev parent reply other threads:[~2019-12-21 8:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 16:29 Can we retire Python 2 now? Markus Armbruster
2019-12-20 16:29 ` Markus Armbruster
2019-12-20 16:56 ` Eduardo Habkost
2019-12-20 16:56 ` Eduardo Habkost
2019-12-21 7:59 ` Markus Armbruster [this message]
2019-12-20 18:56 ` Juan Quintela
2019-12-20 18:56 ` Juan Quintela
2019-12-21 7:57 ` Markus Armbruster
2019-12-21 13:43 ` Paolo Bonzini
2019-12-21 13:43 ` Paolo Bonzini
2019-12-21 18:10 ` Aleksandar Markovic
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=87tv5up0s2.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=ehabkost@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.