Hi Plamen, I suppose we can make autotest work with a dialect compatible with python2.7 and python3.x. The problem however is the man power required to go through the codebase and make the adjustments. Sure, I can make a bunch of semi-automated changes to ease the fine grained work, but testing and getting to a point where it's fully python3 compliant is something that we don't have the resources to go through. Avocado took Cleber, Lukas and Amador many release cycles to get it 100% done.
So let's go with 'no'. Like I said, it's possible to do some changes to ease the work of an interested party, but going all the way to a fully functional python2.7/3.x compliant codebase is something we may never see. Cheers, Lucas On Wed, Apr 11, 2018 at 9:21 PM, Plamen Dimitrov <[email protected]> wrote: > Hi all, > > I know Autotest is not under active development and virt-test is already > deprecated, > but I was still wondering about the future plans on it regarding the > deprecation of python2. > > In particular: > > - upstream Python 2.7 support expires on 2020-01-01 > (https://lwn.net/Articles/750846/) > - there will never be another Python 2.x feature release > (https://legacy.python.org/dev/peps/pep-0404/) > - Fedora is already expiring Python 2 packages wherever possible > (https://lwn.net/Articles/750849/) > > Is there any chance of Autotest possibly moving to python 3 or is the plan to > leave it on > python 2 and let it deprecate in the same way while moving all effort to > avocado? > > I will be glad to hear your thoughts on the matter, > Plamen > > > _______________________________________________ > Autotest-kernel mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/autotest-kernel -- Lucas _______________________________________________ Autotest-kernel mailing list [email protected] https://www.redhat.com/mailman/listinfo/autotest-kernel
