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:
> On Wed, 2019-09-11 at 17:23 +0100, Daniel P. Berrangé wrote:
> > This aligns with fact that the likely future build system
> > we'll use (meson) is written in python, and that python
> > is much more commonly used/understood by developers these
> > days than perl.
>
> I believe Meson is itself implemented in Python 3, so platform
> availability will have to be taken into consideration.
Yes, Meson needs py 3.4 I believe
If I understand the SLES / OpenSUSE situation correctly, then SLES
12.3 should be comparable to OpenSUSE 42.3, which according to
Repology has Python 3.4.6. All other platforms have newer Python 3
versions, so we should be good.
> 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...
--
Andrea Bolognani / Red Hat / Virtualization