Re: Can we retire Python 2 now?
On Saturday, December 21, 2019, Paolo Bonzini 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 > > >
Re: Can we retire Python 2 now?
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
Re: Can we retire Python 2 now?
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/ 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 Reviewed-by: Juan Quintela And anything else that you can think that endorses the change. Later, Juan.
Re: Can we retire Python 2 now?
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-ehabk...@redhat.com/ > > Cc'ing everyone who appears to be maintaining something that looks like > a Python script. > > [*] https://pythonclock.org/ -- Eduardo
Can we retire Python 2 now?
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/
