On Wed, Oct 16, 2019 at 06:48:34PM -0400, John Snow wrote: > > > On 10/16/19 6:42 PM, Eduardo Habkost wrote: > > Python 3.5 is the oldest Python version available on our > > supported build platforms, and Python 2 end of life will be 3 > > weeks after the planned release date of QEMU 4.2.0. Drop Python > > 2 support from configure completely, and require Python 3.5 or > > newer. > > > > Signed-off-by: Eduardo Habkost <ehabk...@redhat.com> > > Seems like a good time and place to mention this. Kevin, you require > 3.6+ for iotests, which are -- at present -- invoked as part of "make > check". > > Do we care? Basically, this just means that iotests won't run for > systems that don't have 3.6+, which would be platforms like Debian 9 -- > which is why ehabkost is choosing 3.5 here.
Depends what the reason for pickin 3.6 was ? Is it really compelling for iotests to require 3.6, or is it easy to support 3.5. I think in general it is desirable to have a consistent story across the codebase for min versions 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 :|
