On Wed, Apr 11, 2018 at 9:58 PM, Chris Evich <[email protected]> wrote: > On 04/11/2018 03:21 PM, Plamen Dimitrov wrote: >> >> 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'm pretty sure this will never happen. Waaaaaay back in the day (years > ago) I asked LMR the same question, he just laughed :D Even with 2.7 > growing long in the tooth, the standard for Autotest was always 2.4 > compatibility.
True, we had to keep 2.4 compatibility for longer than I'd like to admit (RHEL 5, I'm looking at you :)). Nowadays, I'd prefer to leave it 2.7 compliant. > I'm unaware of the Fedora/python2 state, but even so, all currently > supported releases contain python2, as well as RHEL and CentOS. So from > that front, Autotest isn't going away at least within a year or five. > > Though dated, just about all problems are known, and with it in > maintenance-mode, it's a really stable testing framework (some warts > included). Based on the experience we had with avocado, getting the code base 100% python3 compliant is a significant effort. As I said on my e-mail to Plamen, there's low hanging fruit that we can deal with, specially because that first part is semi-automated. It's the details that take the lion's share of the work, and getting all those details right requires a commitment I can't make. I'll take a look at some of the low hanging fruit if work allows me :) Cheers, Lucas _______________________________________________ Autotest-kernel mailing list [email protected] https://www.redhat.com/mailman/listinfo/autotest-kernel
