Andrew Dunstan <[email protected]> writes:
> OK, so the consensus I'm sensing is that we should add a pytest
> framework, backpatch it into all the live branches, and initially port
> some relatively contained set of tests and backpatch that too.
> ...
> This is going to make Python a hard requirement for non-psql based
> testing. There are currently 7 buildfarm animals building master without
> enabling python, although 4 of those are building with meson so
> presumably python is available to them.
Another thing to think about: it's not just "make Python a hard
requirement". It's "make Python >= some-version a hard requirement".
If we intend to be able to back-patch the test framework, that will
constrain our ability to use bleeding-edge Python features in it.
Compare discussions at [1][2].
regards, tom lane
[1]
https://www.postgresql.org/message-id/flat/CAOYmi%2BnVsoMRFp4u0oQ66-oPT6%2BNNAfhLvk5htthY5zkUOnbfA%40mail.gmail.com
[2] https://www.postgresql.org/message-id/flat/16098.1745079444%40sss.pgh.pa.us
