Re: Python 3.5 EOL; when can require 3.6?

[Daniel P . Berrangé]

On Thu, Sep 17, 2020 at 06:07:00PM +0200, Andrea Bolognani wrote:
> On Thu, 2020-09-17 at 17:30 +0200, Markus Armbruster wrote:
> > Thomas Huth <thuth@redhat.com> writes:
> > > Sorry, I forgot to check Debian. If I got that right, Debian 9 still
> > > uses Python 3.5 by default. So I guess that means we can not deprecate
> > > Python 3.5 yet?
> > 
> > Discussed before:
> > 
> >     Subject: Re: [PATCH] qapi: Fix code generation with Python 3.5
> >     Date: Sat, 18 Jan 2020 07:54:18 +0100
> >     Message-ID: <87lfq5s19h.fsf@dusky.pond.sub.org>
> >     https://lists.nongnu.org/archive/html/qemu-devel/2020-01/msg03855.html
> > 
> > Short version: Debian != Debian LTS.  We support Debian until EOL, not
> > LTS.  Debian 9 reached EOL in July.
> 
> FWIW, this is the same policy the libvirt project follows, and we
> have formalized it at
> 
>   https://libvirt.org/platforms.html
> 
> with Debian LTS being called out explicitly as not supported.
> 
> It would be *fantastic* if we could keep the platform support policy
> used by QEMU and libvirt as aligned as reasonably possible.

The current QEMU policy was a copy+paste of the same policy I wrote for
libvirt originally, just adding OpenBSD/NetBSD.

I've just posted an update for QEMU which matches the latest libvirt
policy, again just adding the extra BSDs.

https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06371.html

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 :|