| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Tristan Partin <tristan(at)partin(dot)io>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | pgsql-www <pgsql-www(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Python Tooling |
| Date: | 2026-08-31 20:26:12 |
| Message-ID: | a323d506-699b-4dc5-ad38-9486c4913f9f@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2026-08-31 20:30:17 | Re: Python Tooling |
| Previous Message | Tristan Partin | 2026-08-31 20:25:40 | Re: Broken SSH Key Parsing |