[LTP] [Automated-testing] [RFC] Include runltp-ng (runltp successor) into LTP git

[Andrea Cervesato]

Hi Tim!

On 11/17/22 20:26, Bird, Tim wrote:
> Just one quick bit of feedback...
>
>> -----Original Message-----
>> From: automated-testing@lists.yoctoproject.org <automated-testing@lists.yoctoproject.org> On Behalf Of Andrea Cervesato via
>> lists.yoctoproject.org
>>
>> Hi,
>>
>> as you may know, runltp has been under bug fixing for years without
>> providing any new feature. For this reason the Perl runltp-ng
>> (https://github.com/metan-ucw/runltp-ng) was developed, providing an
>> alternative solution that wasn't completely accepted by LTP community
>> due to the choice of using Perl as the main language.
>>
>> For this reason, a new Python runltp-ng has been developed during this
>> year, with the target to replace Perl version and the current runltp in
>> the next future. Its code can be found here:
>> https://github.com/acerv/runltp-ng
> I think this sounds like a great project, and I look forward to trying it out.
>
>> runltp-ng Python version provides the following features:
>>       - class based architecture in Python 3.6+
> Why python 3.6+?  Fuego uses a docker container with an older
> version of Debian, that defaults to Python version 3.5.3.
Short answer: the 3.5 version reached end-of-life the 5th of September 
2020 (https://www.python.org/downloads/release/python-3510/). Since 
runltp-ng is a new tool, I thought that it was a good idea to start with 
maintained python versions. But we can discuss about it of course.
> Is there something specifically in Python 3.6 that is required for runltp-ng?
> Could it be avoided so that runltp-ng could be backward compatible with
> older interpreters?
>
> (Sorry, but this is one of my pet peeves about the whole Python ecosystem - the lack of
> backward compatibility, and the constant need to be creating virtual environments
> for basic tools and apps.)
>   -- Tim
>
Andrea