On Fri, 2019-09-13 at 10:12 +0100, Daniel P. Berrangé wrote:
On Fri, Sep 13, 2019 at 11:09:16AM +0200, Andrea Bolognani wrote:
> On Fri, 2019-09-13 at 09:59 +0100, Daniel P. Berrangé wrote:
> > On Fri, Sep 13, 2019 at 10:56:45AM +0200, Andrea Bolognani wrote:
> > > My hope is that we can finally ditch Python 2 for good. The
> > >
https://pythonclock.org/ keeps ticking...
> >
> > My intention was to submit patches to purge Py2 support in
> > December, so that we have it gone for the Jan 15 2020 release
> > which matches the pythonclock timeout nicely.
>
> The reason I brought it up is because I don't think the situation
> is going to change significantly in the next three months, so it
> would probably make sense for these replacement Python scripts to
> be Python 3 only from day one.
>
> On the other hand, you've already gone through the trouble of
> making them Python 2.7 compatible...
Honestly the only "trouble" I took was adding
from __future__ import print_function
everything else I just wrote in the normal way & I got lucky that nothing
I did was py3 specific. Most of these scripts are using very boring python
code, so its not that surprising.
Good to know! Still, no need to wait until December before dropping
Python 2 support in my opinion: we should either be able to do it
right now, or we're going to find ourselves in an interesting
position three and a half short months from now... Let's see what
Jim has to say about SUSE :)
--
Andrea Bolognani / Red Hat / Virtualization