Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On Sat, 2019-11-16 at 00:35 +, Jim Fehlig wrote: > On 9/13/19 9:28 AM, Andrea Bolognani wrote: > > [...] you're definitely going to have to: > > > >* add OpenSUSE 12 and 15 to inventory and host_vars/; > > > >* write an AutoYaST configuration file that can be used to install > > a minimal OpenSUSE guest without user interaction and add it to > > the configs/ directory along with the existing preseed and > > kickstart configurations; > > > >* add mappings from abstract package names, such as 'dtrace', to > > the corresponding OpenSUSE concrete package names, such as > > 'systemtap-sdt-devel', to vars/mappings.yml; > > I've completed these steps. > > >* test installation and see what breaks, fix it, rinse and > > repeat :D > > But I'm still in the wash, rinse, repeat cycle :-). I'm able to 'lcitool > install' an openSUSE Leap 15.1 guest, still working on 'lcitool update'. > > Nonetheless I thought I'd send out my WIP before calling it a week. Any > comments > on what I have thus far is appreciated. Do you mind sendind the patch out as an RFC against the libvirt-jenkins-ci project? That way I can conveniently add comments there instead of hijacking this unrelated thread further :) -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On 9/13/19 9:28 AM, Andrea Bolognani wrote: > On Fri, 2019-09-13 at 13:58 +, Jim Fehlig wrote: >> On 9/13/19 2:56 AM, Andrea Bolognani wrote: >>> Jim, does SLES 12 have >>> Python 3? >> >> Yes, python 3.4.6. And python 2.7.13. > > That's *amazing* news! \o/ > >>> And, as a side note: do you think you could find the time to add >>> OpenSUSE support to the libvirt-jenkins-ci project? That'd be very >>> useful, because it makes grepping for this kind of information >>> trivial, and also would open the door to running actual CI jobs on >>> the OS :) >> >> I have internal jobs but agreed it would be nice to have openSUSE included in >> upstream CI on vanilla upstream :-). Any pointers on how to do that? Sorry for the delay. Thanks again for the below info! > Good to hear you're willing to help with this effort! I've been > wanting to introduce OpenSUSE support myself for a very long time, > but unfortunately I've never quite managed to scrap together the > necessary time. > > The repository is > >https://libvirt.org/git/?p=libvirt-jenkins-ci.git > > and most of the stuff you'd have to touch is inside the guests/ > subdirectory; more specifically, you're definitely going to have to: > >* add OpenSUSE 12 and 15 to inventory and host_vars/; > >* write an AutoYaST configuration file that can be used to install > a minimal OpenSUSE guest without user interaction and add it to > the configs/ directory along with the existing preseed and > kickstart configurations; > >* add mappings from abstract package names, such as 'dtrace', to > the corresponding OpenSUSE concrete package names, such as > 'systemtap-sdt-devel', to vars/mappings.yml; I've completed these steps. >* test installation and see what breaks, fix it, rinse and > repeat :D But I'm still in the wash, rinse, repeat cycle :-). I'm able to 'lcitool install' an openSUSE Leap 15.1 guest, still working on 'lcitool update'. Nonetheless I thought I'd send out my WIP before calling it a week. Any comments on what I have thus far is appreciated. Regards, Jim From 9a8923c32301cab40151097508ae7fb2eca2e3b4 Mon Sep 17 00:00:00 2001 From: Jim Fehlig Date: Fri, 15 Nov 2019 15:59:45 -0700 Subject: [PATCH] Add support for openSUSE Leap 15.1 Signed-off-by: Jim Fehlig --- guests/configs/autoinst.xml | 75 +++ .../libvirt-opensuse-15.1/docker.yml | 2 + .../libvirt-opensuse-15.1/install.yml | 2 + .../host_vars/libvirt-opensuse-15.1/main.yml | 22 ++ guests/inventory | 1 + guests/lcitool| 2 + guests/vars/mappings.yml | 38 +- 7 files changed, 140 insertions(+), 2 deletions(-) diff --git a/guests/configs/autoinst.xml b/guests/configs/autoinst.xml new file mode 100644 index 000..d3bdb5c --- /dev/null +++ b/guests/configs/autoinst.xml @@ -0,0 +1,75 @@ + + +http://www.suse.com/1.0/yast2ns; + xmlns:config="http://www.suse.com/1.0/configns;> + + + false + + + + + /dev/vda + all + + + swap + 500M + swap + + + ext4 + / + max + + + + + +UTC +UTC + + + + +http://download.opensuse.org/distribution/leap/15.1/repo/oss/ +repo-oss + + +http://download.opensuse.org/update/leap/15.1/oss +repo-update + + +http://download.opensuse.org/distribution/leap/15.1/repo/non-oss/ +repo-non-oss + + +http://download.opensuse.org/update/leap/15.1/non-oss/ +repo-update-non-oss + + + + +false + + base + minimal_base + yast2_basis + + + +true + + + + root + root + false + 0 + 0 + /root + /bin/bash + + + diff --git a/guests/host_vars/libvirt-opensuse-15.1/docker.yml b/guests/host_vars/libvirt-opensuse-15.1/docker.yml new file mode 100644 index 000..1fcbc38 --- /dev/null +++ b/guests/host_vars/libvirt-opensuse-15.1/docker.yml @@ -0,0 +1,2 @@ +--- +docker_base: openSUSE:15.1 diff --git a/guests/host_vars/libvirt-opensuse-15.1/install.yml b/guests/host_vars/libvirt-opensuse-15.1/install.yml new file mode 100644 index 000..d0fdbe5 --- /dev/null +++ b/guests/host_vars/libvirt-opensuse-15.1/install.yml @@ -0,0 +1,2 @@ +--- +install_url: http://download.opensuse.org/distribution/leap/15.1/repo/oss/ diff --git a/guests/host_vars/libvirt-opensuse-15.1/main.yml b/guests/host_vars/libvirt-opensuse-15.1/main.yml new file mode 100644 index 000..cdd4509 --- /dev/null +++ b/guests/host_vars/libvirt-opensuse-15.1/main.yml @@ -0,0 +1,22 @@ +--- +projects: + - libosinfo + - libvirt + - libvirt-cim + - libvirt-dbus + - libvirt-glib + - libvirt-perl + - libvirt-python + - libvirt-sandbox + - libvirt-tck + - osinfo-db + -
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On Fri, 2019-09-13 at 18:24 +, Jim Fehlig wrote: > On 9/13/19 9:28 AM, Andrea Bolognani wrote: > > Good to hear you're willing to help with this effort! I've been > > wanting to introduce OpenSUSE support myself for a very long time, > > but unfortunately I've never quite managed to scrap together the > > necessary time. > > Thanks for the detailed info! I have a busy month ahead, including traveling > the > next two weeks, so I likely wont get to it until Oct. But I will get to it > :-). No need to rush! :) -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On 9/13/19 9:28 AM, Andrea Bolognani wrote: > On Fri, 2019-09-13 at 13:58 +, Jim Fehlig wrote: >> On 9/13/19 2:56 AM, Andrea Bolognani wrote: >>> Jim, does SLES 12 have >>> Python 3? >> >> Yes, python 3.4.6. And python 2.7.13. > > That's *amazing* news! \o/ > >>> And, as a side note: do you think you could find the time to add >>> OpenSUSE support to the libvirt-jenkins-ci project? That'd be very >>> useful, because it makes grepping for this kind of information >>> trivial, and also would open the door to running actual CI jobs on >>> the OS :) >> >> I have internal jobs but agreed it would be nice to have openSUSE included in >> upstream CI on vanilla upstream :-). Any pointers on how to do that? > > Good to hear you're willing to help with this effort! I've been > wanting to introduce OpenSUSE support myself for a very long time, > but unfortunately I've never quite managed to scrap together the > necessary time. Thanks for the detailed info! I have a busy month ahead, including traveling the next two weeks, so I likely wont get to it until Oct. But I will get to it :-). Regards, Jim > > The repository is > >https://libvirt.org/git/?p=libvirt-jenkins-ci.git > > and most of the stuff you'd have to touch is inside the guests/ > subdirectory; more specifically, you're definitely going to have to: > >* add OpenSUSE 12 and 15 to inventory and host_vars/; > >* write an AutoYaST configuration file that can be used to install > a minimal OpenSUSE guest without user interaction and add it to > the configs/ directory along with the existing preseed and > kickstart configurations; > >* add mappings from abstract package names, such as 'dtrace', to > the corresponding OpenSUSE concrete package names, such as > 'systemtap-sdt-devel', to vars/mappings.yml; > >* test installation and see what breaks, fix it, rinse and > repeat :D > > There are more steps necessary to reach full integration after the > above, such as ensuring Dockerfiles can be generated, figuring out > which projects can be build on the new target platforms and tweaking > the Jenkins / Ansible configuration, but the above is a good start > and also the part that I'm less comfortable doing myself since I'm > not at all familiar with SUSE, so if you could take care of the > above that'd be a big help indeed! > > The guests/README.md file provides some more information, and the > lcitool script is hopefully not too difficult to understand. Last > but not least, if you have any questions you already know how to > get in touch with me ;) > -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On Fri, 2019-09-13 at 13:58 +, Jim Fehlig wrote: > On 9/13/19 2:56 AM, Andrea Bolognani wrote: > > Jim, does SLES 12 have > > Python 3? > > Yes, python 3.4.6. And python 2.7.13. That's *amazing* news! \o/ > > And, as a side note: do you think you could find the time to add > > OpenSUSE support to the libvirt-jenkins-ci project? That'd be very > > useful, because it makes grepping for this kind of information > > trivial, and also would open the door to running actual CI jobs on > > the OS :) > > I have internal jobs but agreed it would be nice to have openSUSE included in > upstream CI on vanilla upstream :-). Any pointers on how to do that? Good to hear you're willing to help with this effort! I've been wanting to introduce OpenSUSE support myself for a very long time, but unfortunately I've never quite managed to scrap together the necessary time. The repository is https://libvirt.org/git/?p=libvirt-jenkins-ci.git and most of the stuff you'd have to touch is inside the guests/ subdirectory; more specifically, you're definitely going to have to: * add OpenSUSE 12 and 15 to inventory and host_vars/; * write an AutoYaST configuration file that can be used to install a minimal OpenSUSE guest without user interaction and add it to the configs/ directory along with the existing preseed and kickstart configurations; * add mappings from abstract package names, such as 'dtrace', to the corresponding OpenSUSE concrete package names, such as 'systemtap-sdt-devel', to vars/mappings.yml; * test installation and see what breaks, fix it, rinse and repeat :D There are more steps necessary to reach full integration after the above, such as ensuring Dockerfiles can be generated, figuring out which projects can be build on the new target platforms and tweaking the Jenkins / Ansible configuration, but the above is a good start and also the part that I'm less comfortable doing myself since I'm not at all familiar with SUSE, so if you could take care of the above that'd be a big help indeed! The guests/README.md file provides some more information, and the lcitool script is hopefully not too difficult to understand. Last but not least, if you have any questions you already know how to get in touch with me ;) -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On Wed, Sep 11, 2019 at 05:23:09PM +0100, Daniel P. Berrangé wrote: > This series is an effort to reduce the number of different > languages we use by eliminating most use of perl in favour > of python. > > 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. > > With this applied we use perl in a handful of places only: BTW, after the first 3, these patches are all independant so can be applied in any order at any time, so no need to review it all for a big bang merge. Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On 9/13/19 3:09 AM, Andrea Bolognani wrote: > If I understand the SLES / OpenSUSE situation correctly, then SLES > 12.3 should be comparable to OpenSUSE 42.3, Nice job! Even SUSE folks are known to get confused by the numbering :-). openSUSE 42.3 ~= SLES12 SP3 SLES12 SP4 and SP5 have no openSUSE equivalent openSUSE 15 ~= SLES15 openSUSE 15.1 ~= SLES15 SP1 openSUSE 15.2 ~= SLES15 SP2 ... openSUSE 16 ~= SLES16 (assumed, since they don't exist) Regards, Jim -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On 9/13/19 2:56 AM, Andrea Bolognani wrote: > On Wed, 2019-09-11 at 17:23 +0100, Daniel P. Berrangé wrote: >> This series is an effort to reduce the number of different >> languages we use by eliminating most use of perl in favour >> of python. > > Just today I found out about > > > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.7_release_notes/new_features#enhancement_compiler-and-tools > > which means that if we interpret "supporting RHEL 7" as "supporting > the most recent RHEL 7 point release", which I believe we do, then > that's one less platform where we are forced to use Python 2! \o/ > > It might even be the last one, but I'm not entirely sure what the > situation is like for SLES and OpenSUSE... Jim, does SLES 12 have > Python 3? Yes, python 3.4.6. And python 2.7.13. > And, as a side note: do you think you could find the time to add > OpenSUSE support to the libvirt-jenkins-ci project? That'd be very > useful, because it makes grepping for this kind of information > trivial, and also would open the door to running actual CI jobs on > the OS :) I have internal jobs but agreed it would be nice to have openSUSE included in upstream CI on vanilla upstream :-). Any pointers on how to do that? Regards, Jim -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On Fri, 2019-09-13 at 10:40 +0100, Daniel P. Berrangé wrote: > On Fri, Sep 13, 2019 at 11:31:34AM +0200, Andrea Bolognani wrote: > > 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 :) > > I don't see a need to rush into it right now. Synchronizing with end of > life of python upstream, makes sense as a time point and matches what > QEMU will doo too, with its first release of 2020 dropping py2. Sure, that sounds fine as long as we've made sure we're ready for the switch when the time comes. -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On Fri, Sep 13, 2019 at 11:31:34AM +0200, Andrea Bolognani wrote: > 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 :) I don't see a need to rush into it right now. Synchronizing with end of life of python upstream, makes sense as a time point and matches what QEMU will doo too, with its first release of 2020 dropping py2. Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
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 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
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: > > > 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... 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. Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
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 -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
On Wed, 2019-09-11 at 17:23 +0100, Daniel P. Berrangé wrote: > This series is an effort to reduce the number of different > languages we use by eliminating most use of perl in favour > of python. Just today I found out about https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.7_release_notes/new_features#enhancement_compiler-and-tools which means that if we interpret "supporting RHEL 7" as "supporting the most recent RHEL 7 point release", which I believe we do, then that's one less platform where we are forced to use Python 2! \o/ It might even be the last one, but I'm not entirely sure what the situation is like for SLES and OpenSUSE... Jim, does SLES 12 have Python 3? And, as a side note: do you think you could find the time to add OpenSUSE support to the libvirt-jenkins-ci project? That'd be very useful, because it makes grepping for this kind of information trivial, and also would open the door to running actual CI jobs on the OS :) > 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. My hope is that we can finally ditch Python 2 for good. The https://pythonclock.org/ keeps ticking... -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 00/24] scripts: convert most perl scripts to python
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 series is an effort to reduce the number of different > > languages we use by eliminating most use of perl in favour > > of python. > > Just today I found out about > > > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/7.7_release_notes/new_features#enhancement_compiler-and-tools > > which means that if we interpret "supporting RHEL 7" as "supporting > the most recent RHEL 7 point release", which I believe we do, then > that's one less platform where we are forced to use Python 2! \o/ I should have said that I did in fact test this series with Python 2.7, Python 3.5 and Python 3.7 - all using the Fedora 31 RPMS of these respective versions. > > 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 > 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. Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
