We are working now on porting ovirt-imageio to python 3. One nasty issue is having to ovirt-imageio-proxy, running on engine host on CentOS/RHEL >= 7.7 - with python 2.7.
Supporting both python 2.7 and 3 is major pain (complicated build, new packages names) and we like to avoid this. We can switch to python 3 only, if we use the new python 3.6 package added in 7.7. Maybe we can do the same for otopi/engine-setup? Do you see any issue with this? Nir
_______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/A6FHTTNQQQ3IXQXZV6JHTYEVI7JPCQCK/
