From: Jonathan S. Katz <jkatz@postgresql.org>
To: Tristan Partin <tristan@partin.io>
To: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-www <pgsql-www@lists.postgresql.org>
Subject: Re: Python Tooling
Date: Mon, 31 Aug 2026 16:26:12 -0400
Message-ID: <a323d506-699b-4dc5-ad38-9486c4913f9f@postgresql.org> (raw)
In-Reply-To: <DL3ERUXYGQHP.39871YBG1FDON@partin.io>
References: <DKRCOG3ADVJF.3LG0UBOL3J14S@partin.io>
<CABUevEzLcU3EiZXE5GYAZU44nd0KmRQnFS2ymmRgaan5Y4Bbhw@mail.gmail.com>
<DL3ERUXYGQHP.39871YBG1FDON@partin.io>
On 8/31/26 4:23 PM, Tristan Partin wrote:
>> The basic answer is, "use whatever is in debian" because that's what it's
>> deployed on, and at this point that's trixie.
>>
>> That also means we do *not* want to change the dependencies to anything
>> other than whatr's there.
>
> Does this mean that we rely on the versions of Python packages within
> Trixie and the requirements.txt is basically ignored?
FWIW I will use requirements.txt in my local environment, but that only
happens when it gets nuked, so it's a once-every-few-years ordeal.
(I could probably get the pgweb env to load from a container; perhaps
this is a suggestion towards a Dockerfile?)
Jonathan
Attachments:
OpenPGP_signature.asc (application/pgp-signature, 839B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-www@postgresql.org
Cc: jkatz@postgresql.org, tristan@partin.io, magnus@hagander.net, pgsql-www@lists.postgresql.org
Subject: Re: Python Tooling
In-Reply-To: <a323d506-699b-4dc5-ad38-9486c4913f9f@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox