On Thu, Nov 29, 2018, 13:25 Yedidyah Bar David <[email protected] wrote: > Hi all, > > As some of you might recall, some time ago we made otopi default to > python3, and quickly reverted that, realizing this causes too much > breakage. > > Now things should hopefully be more stable, and I now merged a patch > to default to python3 again.
> Current status: > > engine-setup works with python3 on fedora. > > host-deploy works with python3 on fedora, with both engine being on > el7 and on fedora. Didn't try on el7, might work as well. I hope that "might work" good enough :-) hosted-engine --deploy is most likely broken on fedora, but I think it > was already broken. We are working on that, but it will require some > more time - notably, having stuff from vdsm on python3 vdsm is not available on python 3, but this should not be a problem since you should not import anything from vdsm. You should use only the vdsmclient package to connect to vdsm and use vdsm public APIs. But even this library is not available yet for python 3. (if not fully > porting vdsm to python3, which I understand will take even more time). And we need also sanlock, ioprocess, mom, and ovirt-imageio for python 3. > If you want to use python2, you can do that with: > > OTOPI_PYTHON=/bin/python hosted-engine --deploy > Why not keep it using python 2 and provide option to use py3? 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/APZVCP66D3L52OAOOT3WOR2TGZYJJFIK/
