| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org> |
| Cc: | Devrim Gündüz <devrim(at)gunduz(dot)org>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG20 Minimum Dependency Thread |
| Date: | 2026-07-17 08:28:24 |
| Message-ID: | CAGECzQRwrEU2bGRYhd=X=3X=tJNoA+eEMs1kgXOkDJNOx8Tr1g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 16 Jul 2026 at 18:54, Christoph Berg <myon(at)debian(dot)org> wrote:
> Yes, everything should be in-distro. We can make exceptions and supply
> backports via apt.postgresql.org, but they should be rare. And really
> only be for isolated things like I've just started supplying updated
> geos libraries for postgis. I wouldn't want to backport a core package
> like python.
Just to be totally clear on what I meant: It's not about the "python"
package. I'm specifically talking about "python3-pytest" package.
Pytest is a test-runner for Python. It's fully written using python.
The "python3-pytest" package contains a fixed pytest version. However
there are newer pytest versions available on pip that are compatible
with the "python" package shipped by Debian.
It sounds like us supporting the official python3-pytest version is
the heavily preferred approach.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-07-17 08:36:45 | Re: PGLZ Compression Optimization |
| Previous Message | Thom Brown | 2026-07-17 08:26:39 | Re: [PATCH] Rename "getdatabaseencoding()" to "pg_database_encoding()", and document |