| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Direction for test frameworks: Perl TAP vs. Python/pytest |
| Date: | 2026-06-16 14:38:53 |
| Message-ID: | 72023f0f-fb4c-4b13-b3e3-6a517ec1e7d3@iki.fi |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2026-06-16 15:07:18 | Re: Direction for test frameworks: Perl TAP vs. Python/pytest |
| Previous Message | Nathan Bossart | 2026-06-16 14:38:24 | Re: mxid_score can become Infinity in pg_stat_autovacuum_scores |