| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Subject: | Re: Direction for test frameworks: Perl TAP vs. Python/pytest |
| Date: | 2026-06-16 15:54:34 |
| Message-ID: | CAOYmi+=67YhT-utixXKvaHXo1yZJcDQMNQPWtAO9rrybXPQT9w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 16, 2026 at 8:41 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm starting to think that we'd thank ourselves in the long run
> if we did do the conversion in all branches at once.
Avoiding the "big bang" port was one of the reasons I proposed adding
a Python suite that only does things we don't currently do in Perl (a
pared-down option B, plus Test::Session). That way, we shake out the
Python deployment/maintenance questions and begin to develop a shared
vocabulary *before* the entirety of the test suite starts depending on
it.
That wouldn't preclude an eventual flag day, if we decided to. But if
Python can land and be developed while other people are continuing to
hack on features and backport tests, I think that's more likely to
succeed. I agree with Melanie; I really don't want people to hate
this.
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-06-16 16:02:09 | Re: Direction for test frameworks: Perl TAP vs. Python/pytest |
| Previous Message | Daniel Gustafsson | 2026-06-16 15:54:28 | Re: Direction for test frameworks: Perl TAP vs. Python/pytest |