[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 7/7] Python: Drop support for Python 3.6
From: |
John Snow |
Subject: |
Re: [PATCH 7/7] Python: Drop support for Python 3.6 |
Date: |
Thu, 9 Feb 2023 16:15:11 -0500 |
On Thu, Feb 9, 2023 at 1:03 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> On Thu, Feb 09, 2023 at 11:40:57AM -0500, John Snow wrote:
> > On Thu, Feb 9, 2023 at 11:27 AM Daniel P. Berrangé <berrange@redhat.com>
> > wrote:
> > >
> > > On Thu, Feb 09, 2023 at 10:40:34AM -0500, John Snow wrote:
> > > > Python 3.6 was EOL 2021-12-31. Newer versions of upstream libraries have
> > > > begun dropping support for this version and it is becoming more
> > > > cumbersome to support. Avocado-framework and qemu.qmp each have their
> > > > own reasons for wanting to drop Python 3.6.
> > > >
> > > > Since it is safe to under our supported platform policy, do so.
> > >
> > > Upstream EOL dates are essentially irrelevant from our platform
> > > support policy for deciding min versions
> > >
> >
> > It's relevant because as other Python packages drop support, the
> > burden of support is pushed onto Cleber and I, as explained in the
> > cover letter. It is not a justification in and of itself, but it
> > summarizes the ecosystem conditions that prompt the desire for the
> > change.
> > > QEMU aims to target released OS distributions, and their vendors
> > > may choose to support software for arbitrarily longer periods of
> > > time than upstream. This extended support is one of the key
> > > value adds of OS distributions.
> > >
> > > To justify dropping python 3.6, the commit message needs to
> > > illustrate that all our targetted distros are capable of
> > > supporting the new proposed new min version.
> >
> > That is the point of this series: illustrating that it is indeed safe
> > to drop Python 3.6. I am not clear on what you are actually requesting
> > as a change.
>
> Essentially it should explain what versions are available in each
> distro. See for example commit 5890258aeeba303704ec1adca415e46067800777.
Ah, OK.
Fedora 36: 3.10.5
Ubuntu 20.04: 3.8.10
Debian 11: 3.9.2
OpenSUSE Leap 15.4 uses 3.6.15, but 3.9 and 3.10 are available with a
simple zypper invocation.
CentOS Stream 8 uses 3.6.8, but 3.8 and 3.9 are available.
CentOS Stream 9 uses 3.9.13.
Alpine: Not sure, but tests pass.
FreeBSD 12: 3.7 (tests/vm/freebsd already uses this version.)
OpenBSD: ?
NetBSD: ?
I can update the commit message, but I do have questions for you in
patch 5 concerning the docker configurations and our test matrix that
I want to work out before a respin.
>
>
>
> With 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 :|
>
- Re: [PATCH 6/7] CI: Stop building docs on centos8, (continued)
[PATCH 3/7] configure: Look for auxiliary Python installations, John Snow, 2023/02/09
[PATCH 4/7] configure: Add nice hint to Python failure message, John Snow, 2023/02/09
[PATCH 7/7] Python: Drop support for Python 3.6, John Snow, 2023/02/09
[PATCH 2/7] Python: drop pipenv, John Snow, 2023/02/09