* Can we retire Python 2 now?
@ 2019-12-20 16:29 Markus Armbruster
2019-12-20 16:56 ` Eduardo Habkost
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Markus Armbruster @ 2019-12-20 16:29 UTC (permalink / raw)
To: qemu-devel
Cc: Paolo Bonzini, Marcelo Tosatti, Stefan Hajnoczi, Peter Maydell,
Eduardo Habkost, Cleber Rosa, Richard Henderson,
Marc-André Lureau, Michael Roth, Fam Zheng, Juan Quintela,
Dr. David Alan Gilbert, Aurelien Jarno, Aleksandar Markovic,
Aleksandar Rikalo, Philippe Mathieu-Daudé,
Fabien Chouteau, KONRAD Frederic, Hervé Poussineau,
Alex Bennée, Kevin Wolf, Max Reitz, kvm, qemu-block,
qemu-ppc
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?
Cc'ing everyone who appears to be maintaining something that looks like
a Python script.
[*] https://pythonclock.org/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Can we retire Python 2 now?
2019-12-20 16:29 Can we retire Python 2 now? Markus Armbruster
@ 2019-12-20 16:56 ` Eduardo Habkost
2019-12-20 18:56 ` Juan Quintela
2019-12-21 13:43 ` Paolo Bonzini
2 siblings, 0 replies; 4+ messages in thread
From: Eduardo Habkost @ 2019-12-20 16:56 UTC (permalink / raw)
To: Markus Armbruster
Cc: qemu-devel, Paolo Bonzini, Marcelo Tosatti, Stefan Hajnoczi,
Peter Maydell, Cleber Rosa, Richard Henderson,
Marc-André Lureau, Michael Roth, Fam Zheng, Juan Quintela,
Dr. David Alan Gilbert, Aurelien Jarno, Aleksandar Markovic,
Aleksandar Rikalo, Philippe Mathieu-Daudé,
Fabien Chouteau, KONRAD Frederic, Hervé Poussineau,
Alex Bennée, Kevin Wolf, Max Reitz, kvm, qemu-block,
qemu-ppc
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 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/
>
> Cc'ing everyone who appears to be maintaining something that looks like
> a Python script.
>
> [*] https://pythonclock.org/
--
Eduardo
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Can we retire Python 2 now?
2019-12-20 16:29 Can we retire Python 2 now? Markus Armbruster
2019-12-20 16:56 ` Eduardo Habkost
@ 2019-12-20 18:56 ` Juan Quintela
2019-12-21 13:43 ` Paolo Bonzini
2 siblings, 0 replies; 4+ messages in thread
From: Juan Quintela @ 2019-12-20 18:56 UTC (permalink / raw)
To: Markus Armbruster
Cc: qemu-devel, Paolo Bonzini, Marcelo Tosatti, Stefan Hajnoczi,
Peter Maydell, Eduardo Habkost, Cleber Rosa, Richard Henderson,
Marc-André Lureau, Michael Roth, Fam Zheng,
Dr. David Alan Gilbert, Aurelien Jarno, Aleksandar Markovic,
Aleksandar Rikalo, Philippe Mathieu-Daudé,
Fabien Chouteau, KONRAD Frederic, Hervé Poussineau,
Alex Bennée, Kevin Wolf, Max Reitz, kvm, qemu-block,
qemu-ppc
Markus Armbruster <armbru@redhat.com> 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?
>
> Cc'ing everyone who appears to be maintaining something that looks like
> a Python script.
>
> [*] https://pythonclock.org/
I am pretty sure that I am not a python maintaainer at all.
But anyways, python3 is only at python3.7.
python3.0 debuted at 2008, so ...
Acked-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
And anything else that you can think that endorses the change.
Later, Juan.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Can we retire Python 2 now?
2019-12-20 16:29 Can we retire Python 2 now? Markus Armbruster
2019-12-20 16:56 ` Eduardo Habkost
2019-12-20 18:56 ` Juan Quintela
@ 2019-12-21 13:43 ` Paolo Bonzini
2 siblings, 0 replies; 4+ messages in thread
From: Paolo Bonzini @ 2019-12-21 13:43 UTC (permalink / raw)
To: Markus Armbruster, qemu-devel
Cc: Marcelo Tosatti, Stefan Hajnoczi, Peter Maydell, Eduardo Habkost,
Cleber Rosa, Richard Henderson, Marc-André Lureau,
Michael Roth, Fam Zheng, Juan Quintela, Dr. David Alan Gilbert,
Aurelien Jarno, Aleksandar Markovic, Aleksandar Rikalo,
Philippe Mathieu-Daudé,
Fabien Chouteau, KONRAD Frederic, Hervé Poussineau,
Alex Bennée, Kevin Wolf, Max Reitz, kvm, qemu-block,
qemu-ppc
On 20/12/19 17:29, 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?
>
> Cc'ing everyone who appears to be maintaining something that looks like
> a Python script.
>
> [*] https://pythonclock.org/
Fortunately Betteridge's law of headlines is not always true. :)
Paolo
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-12-21 13:43 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-20 16:29 Can we retire Python 2 now? Markus Armbruster
2019-12-20 16:56 ` Eduardo Habkost
2019-12-20 18:56 ` Juan Quintela
2019-12-21 13:43 ` Paolo Bonzini
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).