Re: Direction for test frameworks: Perl TAP vs. Python/pytest - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Date
Msg-id 72023f0f-fb4c-4b13-b3e3-6a517ec1e7d3@iki.fi
Whole thread
In response to Direction for test frameworks: Perl TAP vs. Python/pytest  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Re: Direction for test frameworks: Perl TAP vs. Python/pytest
List pgsql-hackers
On 16/06/2026 17:23, Andrew Dunstan wrote:
> (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?

- Heikki




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: use of SPI by postgresImportForeignStatistics
Next
From: Aleksander Alekseev
Date:
Subject: Re: Direction for test frameworks: Perl TAP vs. Python/pytest