qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* 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; 7+ messages in thread
From: Markus Armbruster @ 2019-12-20 16:29 UTC (permalink / raw)
  To: qemu-devel
  Cc: Fam Zheng, Peter Maydell, kvm, KONRAD Frederic, qemu-block,
	Juan Quintela, Michael Roth, Hervé Poussineau,
	Marc-André Lureau, Aleksandar Rikalo,
	Philippe Mathieu-Daudé, Eduardo Habkost,
	Dr. David Alan Gilbert, Fabien Chouteau, Stefan Hajnoczi,
	Cleber Rosa, Alex Bennée, Richard Henderson, Kevin Wolf,
	Marcelo Tosatti, Max Reitz, qemu-ppc, Aleksandar Markovic,
	Paolo Bonzini, Aurelien Jarno

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] 7+ 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-21  7:59   ` Markus Armbruster
  2019-12-20 18:56 ` Juan Quintela
  2019-12-21 13:43 ` Paolo Bonzini
  2 siblings, 1 reply; 7+ messages in thread
From: Eduardo Habkost @ 2019-12-20 16:56 UTC (permalink / raw)
  To: Markus Armbruster
  Cc: Fam Zheng, Peter Maydell, kvm, qemu-devel, KONRAD Frederic,
	qemu-block, Juan Quintela, Michael Roth, Hervé Poussineau,
	Marc-André Lureau, Aleksandar Rikalo,
	Philippe Mathieu-Daudé, Dr. David Alan Gilbert,
	Fabien Chouteau, Stefan Hajnoczi, Cleber Rosa, Alex Bennée,
	Richard Henderson, Kevin Wolf, Marcelo Tosatti, Max Reitz,
	qemu-ppc, Aleksandar Markovic, Paolo Bonzini, Aurelien Jarno

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] 7+ 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  7:57   ` Markus Armbruster
  2019-12-21 13:43 ` Paolo Bonzini
  2 siblings, 1 reply; 7+ messages in thread
From: Juan Quintela @ 2019-12-20 18:56 UTC (permalink / raw)
  To: Markus Armbruster
  Cc: Fam Zheng, Peter Maydell, kvm, qemu-devel, KONRAD Frederic,
	qemu-block, Michael Roth, Hervé Poussineau,
	Marc-André Lureau, Aleksandar Rikalo,
	Philippe Mathieu-Daudé, Eduardo Habkost,
	Dr. David Alan Gilbert, Fabien Chouteau, Stefan Hajnoczi,
	Cleber Rosa, Alex Bennée, Richard Henderson, Kevin Wolf,
	Marcelo Tosatti, Max Reitz, qemu-ppc, Aleksandar Markovic,
	Paolo Bonzini, Aurelien Jarno

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] 7+ messages in thread

* Re: Can we retire Python 2 now?
  2019-12-20 18:56 ` Juan Quintela
@ 2019-12-21  7:57   ` Markus Armbruster
  0 siblings, 0 replies; 7+ messages in thread
From: Markus Armbruster @ 2019-12-21  7:57 UTC (permalink / raw)
  To: Juan Quintela; +Cc: qemu-devel

Juan Quintela <quintela@redhat.com> writes:

> 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.

You are:

    $ scripts/get_maintainer.pl -f scripts/vmstate-static-checker.py
    Juan Quintela <quintela@redhat.com> (maintainer:Migration)
    "Dr. David Alan Gilbert" <dgilbert@redhat.com> (maintainer:Migration)
    Eduardo Habkost <ehabkost@redhat.com> (odd fixer:Python scripts)
    Cleber Rosa <crosa@redhat.com> (odd fixer:Python scripts)
    qemu-devel@nongnu.org (open list:All patches CC here)

Resistance is futile!

[...]



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Can we retire Python 2 now?
  2019-12-20 16:56 ` Eduardo Habkost
@ 2019-12-21  7:59   ` Markus Armbruster
  0 siblings, 0 replies; 7+ messages in thread
From: Markus Armbruster @ 2019-12-21  7:59 UTC (permalink / raw)
  To: Eduardo Habkost; +Cc: qemu-devel

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!



^ permalink raw reply	[flat|nested] 7+ 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
  2019-12-21 18:10   ` Aleksandar Markovic
  2 siblings, 1 reply; 7+ messages in thread
From: Paolo Bonzini @ 2019-12-21 13:43 UTC (permalink / raw)
  To: Markus Armbruster, qemu-devel
  Cc: Fam Zheng, Peter Maydell, kvm, KONRAD Frederic, qemu-block,
	Juan Quintela, Michael Roth, Hervé Poussineau,
	Marc-André Lureau, Aleksandar Rikalo,
	Philippe Mathieu-Daudé, Eduardo Habkost,
	Dr. David Alan Gilbert, Fabien Chouteau, Stefan Hajnoczi,
	Cleber Rosa, Alex Bennée, Richard Henderson, Kevin Wolf,
	Marcelo Tosatti, Max Reitz, qemu-ppc, Aleksandar Markovic,
	Aurelien Jarno

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] 7+ messages in thread

* Re: Can we retire Python 2 now?
  2019-12-21 13:43 ` Paolo Bonzini
@ 2019-12-21 18:10   ` Aleksandar Markovic
  0 siblings, 0 replies; 7+ messages in thread
From: Aleksandar Markovic @ 2019-12-21 18:10 UTC (permalink / raw)
  To: Paolo Bonzini
  Cc: Fam Zheng, Peter Maydell, kvm@vger.kernel.org,
	qemu-devel@nongnu.org, Michael Roth, KONRAD Frederic,
	qemu-block@nongnu.org, Juan Quintela, Markus Armbruster,
	Hervé Poussineau, Marc-André Lureau, Aleksandar Rikalo,
	Philippe Mathieu-Daudé, Eduardo Habkost,
	Dr. David Alan Gilbert, Fabien Chouteau, Stefan Hajnoczi,
	Cleber Rosa, Alex Bennée, Richard Henderson, Kevin Wolf,
	Marcelo Tosatti, Max Reitz, qemu-ppc@nongnu.org,
	Aleksandar Markovic, Aurelien Jarno

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

On Saturday, December 21, 2019, Paolo Bonzini <pbonzini@redhat.com> wrote:

> 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.  :)
>
>
Perhaps we can formulate a new law that says:

"Any person who says that he/she is pretty sure he/she is not a maintainer
of something at all, is, in fact, and for sure, the maintainer of that
thing."

:)

Aleksandar

Paolo
>
>
>

[-- Attachment #2: Type: text/html, Size: 1322 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2019-12-21 18:11 UTC | newest]

Thread overview: 7+ 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-21  7:59   ` Markus Armbruster
2019-12-20 18:56 ` Juan Quintela
2019-12-21  7:57   ` Markus Armbruster
2019-12-21 13:43 ` Paolo Bonzini
2019-12-21 18:10   ` Aleksandar Markovic

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).