Can we retire Python 2 now?

2019-12-20 Thread Markus Armbruster
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://pythonclo

Re: Can we retire Python 2 now?

2019-12-20 Thread Eduardo Habkost
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 hone

Re: Can we retire Python 2 now?

2019-12-20 Thread Juan Quintela
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

Re: Can we retire Python 2 now?

2019-12-21 Thread Paolo Bonzini
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 t

Re: Can we retire Python 2 now?

2019-12-21 Thread Aleksandar Markovic
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?