Re: PG20 Minimum Dependency Thread

On Mon, 22 Jun 2026 at 22:50, Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> I have a much harder time agreeing with this. The end user experience
> we're going for is
>
> $ sudo dnf install python3.12-pytest
> $ meson configure -DPYTEST=pytest-3.12
> $ ninja reconfigure
> ...
> pytest : /usr/bin/pytest-3.12 7.4.2
> ...
> plpython : YES 3.9
>
> That's not a burden.

+1. I don't see why we must accommodate the Python version the OS
originally shipped with if the OS also provides official packages for
newer versions. We're fine with requiring people to install packages
that are not part of the base OS image for other things (gcc/make/etc)
why not for pytest.

Note that in my testing of Rocky9 (from a fresh docker install) I
needed the following two additional commands before I could install
python3.12-pytest with dnf:

$ dnf install 'dnf-command(config-manager)'
$ dnf config-manager --enable crb

I'm not entirely sure how (un)common those steps are for RHEL users.
To be clear python3.12 is installable without those steps, just not
python3.12-pytest.

On Wed, 8 Jul 2026 at 19:30, Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> If we did that, Python 3.9 looks within reach for PG20, which seems
> reasonable considering it'll already have been dead for two years. (It
> looks like LTS support for a spectrum of Pythons is now the norm
> rather than the exception, and we should start making decisions
> accordingly.) That'd only be a roadbump for our SUSE buildfarm owners,
> who'd need to install an additional package beside the base Python 3.6
> in order to run Python scripts.

You seem to be walking back on your previous email here by applying
that logic only to SUSE/SLES. If we applied that logic to all
operating systems, we'd end up on Python 3.11 (based on your list).