qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Python 3.5 EOL; when can require 3.6?


From: Eduardo Habkost
Subject: Re: Python 3.5 EOL; when can require 3.6?
Date: Thu, 17 Sep 2020 12:50:49 -0400

On Thu, Sep 17, 2020 at 05:33:15PM +0100, Daniel P. Berrangé wrote:
> On Thu, Sep 17, 2020 at 12:19:19PM -0400, Eduardo Habkost wrote:
> > On Wed, Sep 16, 2020 at 04:00:14PM +0200, Thomas Huth wrote:
> > > On 16/09/2020 14.30, Peter Maydell wrote:
> > > > On Wed, 16 Sep 2020 at 08:43, Markus Armbruster <armbru@redhat.com> 
> > > > wrote:
> > > >> We require Python 3.5.  It will reach its "end of life" at the end of
> > > >> September 2020[*].  Any reason not to require 3.6 for 5.2?  
> > > >> qemu-iotests
> > > >> already does for its Python parts.
> > > [...]
> > > > The default should be
> > > > "leave the version dependency where it is", not "bump the version
> > > > dependency as soon as we can".
> > > 
> > > OTOH, if none of our supported build systems uses python 3.5 by default
> > > anymore, it also will not get tested anymore, so bugs might creep in,
> > > which will of course end up in a bad experience for the users, too, that
> > > still try to build with such an old version. So limiting the version to
> > > the level that we also test is IMHO very reasonable.
> > > 
> > > Let's have a look at the (older) systems that we support and the python
> > > versions according to repology.org:
> > > 
> > > - RHEL7 / CentOS 7 : 3.6.8
> > > - Ubuntu 18.04 (Bionic) : >= 3.6.5
> > > - openSUSE Leap 15.0 : >= 3.6.5
> > > - OpenBSD Ports : >= 3.7.9
> > > - FreeBSD Ports : >= 3.5.10 - but there is also 3.6 or newer
> > > - Homebrew : >= 3.7.9
> > > 
> > > ... so I think it should be fine to retire 3.5 nowadays.
> > 
> > Thank you very much for the summary.  I've added this info to
> > https://wiki.qemu.org/Supported_Build_Platforms
> > 
> > Has anybody been able to find information om SLES Python
> > versions?  I can't find this anywhere.
> 
> It is slightly tedious, but I was pointed at
> 
>   https://scc.suse.com/api/package_search/products
> 
> where you find the product ID.
> 
> eg SLES 15  is ID 1609
> 
> which you can plug into
> 
> https://scc.suse.com/api/package_search/packages?product_id=1609&amp;query=python

Thanks!

> 
> and that somes some package names like "libpython3_6" so 3.6.5
> looks like a match,

$ curl -s 
'https://scc.suse.com/api/package_search/packages?product_id=1609&query=python' 
| \
  jq -r '.data[] | select(.name | match("^python[0-9]*$")) | "\(.name) 
\(.version) \(.arch)"'
python 2.7.17 x86_64
python 2.7.14 x86_64
python 2.7.14 x86_64
python 2.7.14 x86_64
python 2.7.14 x86_64
python 2.7.14 x86_64
python 2.7.14 x86_64
python 2.7.14 x86_64
python 2.7.14 x86_64
python3 3.6.9 x86_64
python3 3.6.8 x86_64
python3 3.6.8 x86_64
python3 3.6.5 x86_64
python3 3.6.5 x86_64
python3 3.6.5 x86_64
python3 3.6.5 x86_64
python3 3.6.10 x86_64

I've updated the wiki with 3.6.10.

> 
> This looks like it matches openSUSE Leap 15, which suggest we
> probably don't need to look at SLES directly.
> 
> 
> SLES 15 was released in July 2018, so with our 2 year overlap for the
> previous release, we can consider SLES 12sp2 unsupported from this
> release cycle.

I've updated the wiki to indicate that.  Thanks for the reminder.

-- 
Eduardo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]