Re: Direction for test frameworks: Perl TAP vs. Python/pytest

Hi,

> > (A) Wholesale port with a flag day -- Python becomes *the*
> > framework, migrate the existing tests, stop accepting and eventually
> > remove the Perl one. One framework to learn and maintain, but a
> > large disruptive change with real dependency questions (which
> > Python, which libpq binding, buildfarm minimums).
> +1 on this
>
> I don't mind keeping the existing Perl tests for a while, but I'd like
> all new tests to be in Python, and have an agreement to migrate all
> existing tests over time. I haven't really looked at these efforts in
> detail so I don't know how long a transition period we need. Months? Years?

+1

I don't think we necessarily need a strict deadline on migrating
completely to Python. We will eventually and it doesn't look like Perl
tests require that much effort in terms of maintenance.

--
Best regards,
Aleksander Alekseev