Re: Python 3.5 EOL; when can require 3.6?

[Daniel P . Berrangé]

On Wed, Sep 16, 2020 at 11:50:06AM +0200, Thomas Huth wrote:
> On 16/09/2020 10.33, Daniel P. Berrangé wrote:
> > On Wed, Sep 16, 2020 at 09:54:32AM +0200, Thomas Huth wrote:
> >> On 16/09/2020 09.43, Markus Armbruster 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.
> >>
> >> I think the only reason for requiring Python 3.5 is that we still use
> >> Ubuntu Xenial in Travis. We don't support Xenial according to our
> >> support policy anymore, but we did not update to Bionic there since it
> >> has that broken version of libssh.
> >>
> >> Fortunately, since a couple of weeks, Travis now supports Focal, too, so
> >> once we switched our .travis.yml to use Focal, I think we could start
> >> requiring Python 3.6.
> > 
> > Note we really should not be constrained by what Travis provides as
> > images. Travis images provide docker, so we can spawn our Travis
> > jobs inside containers to get arbitrary linux distros. We did this
> > for libvirt for a while until we switched to GitLab CI. So we
> > definitely don't need to care about Xenial from a Travis POV no
> > matter what.
> 
> I hope we could finally exploit the possibility to use KVM on Travis ...
> that won't be possible anymore once we use containers there.

Do they forbid passing the /dev/kvm device node into the docker
container ? I would have though that would be allowed, since using
KVM inside docker is no worse than using it outside docker in the
Travis env.

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