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

From Jacob Champion
Subject Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Date
Msg-id CAOYmi+=67YhT-utixXKvaHXo1yZJcDQMNQPWtAO9rrybXPQT9w@mail.gmail.com
Whole thread
In response to Re: Direction for test frameworks: Perl TAP vs. Python/pytest  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Direction for test frameworks: Perl TAP vs. Python/pytest
List pgsql-hackers
On Tue, Jun 16, 2026 at 8:41 AM Tom Lane <tgl@sss.pgh.pa.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



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Next
From: Tom Lane
Date:
Subject: Re: Direction for test frameworks: Perl TAP vs. Python/pytest