On Thu, Feb 12, 2026 at 10:39 AM Rainer Jung <[email protected]> wrote: > > 2nd attempt, had sent it to the OP instead of the list. > > Am 12.02.26 um 09:17 schrieb Giannis Christodoulou: > > Hello, > > > > Thanks for the answer and the responsiveness. > > Just one more clarification, the answer to which test suite should be > > enhanced in each case lies in the already covered areas (modules) > > of each test suite or is there a preference for the python based one to > > gradually make it support more test cases and modules? > > My personal opinion: the perl based suite will not go away soon and has > a lot of value due to the many tests it runs. The barrier for > contribution might be lower for the python based tests. So > > - choose according to the tested modules/functionality > > - if adding to the perl based test suite turns out to be too demanding > for you and the python based one is much simpler for you, adding tests > there might be better than adding them nowhere.
I only add to the perl suite because I am familiar with it and more literate in Perl than Python (despite recognizing that python is much better) It is relatively easy to find something similar to what you need and copy it. The python suite did not work on my AIX systems (python too old?) where I try to test releases, so I am not even in the habit of running it. I think it's fine to favor the python suite for new tests / new contributors, especially if we can put together better and better simple examples there. -- Eric Covener [email protected]
