pg.ddx.io  pgsql-www@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tristan Partin <tristan@partin.io>
To: Jonathan S. Katz <jkatz@postgresql.org>
To: Magnus Hagander <magnus@hagander.net>
Cc: pgsql-www <pgsql-www@lists.postgresql.org>
Subject: Re: Python Tooling
Date: Mon, 31 Aug 2026 20:32:31 +0000
Message-ID: <DL3EYFR4ZDXM.R13R00LPMM7T@partin.io> (raw)
In-Reply-To: <a323d506-699b-4dc5-ad38-9486c4913f9f@postgresql.org>
References: <DKRCOG3ADVJF.3LG0UBOL3J14S@partin.io>
	<CABUevEzLcU3EiZXE5GYAZU44nd0KmRQnFS2ymmRgaan5Y4Bbhw@mail.gmail.com>
	<DL3ERUXYGQHP.39871YBG1FDON@partin.io>
	<a323d506-699b-4dc5-ad38-9486c4913f9f@postgresql.org>

On Mon Aug 31, 2026 at 8:26 PM UTC, Jonathan S. Katz wrote:
> 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?)

Are you referring to deploying as a container or a devcontainer? To 
expand on what I am thinking that we should use native Python tooling to 
manage dependencies. For instance, we would encode all our dependencies 
in the pyproject.toml, and then actually run the server with `uv run 
...`.

Python tooling moves so much faster than Debian that I don't think it 
makes sense to depend on Debian for anything other than the base OS and 
maybe the Python interpreter.

-- 
Tristan Partin
PostgreSQL Contributors Team
AWS (https://aws.amazon.com)





view thread (9+ messages)  latest in thread

Message-ID: <DL3EYFR4ZDXM.R13R00LPMM7T@partin.io>
Permalink:  ../DL3EYFR4ZDXM.R13R00LPMM7T@partin.io/
Also on:    postgresql.org/message-id/DL3EYFR4ZDXM.R13R00LPMM7T@partin.io

 · 

reply

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: tristan@partin.io, jkatz@postgresql.org, magnus@hagander.net, pgsql-www@lists.postgresql.org
  Subject: Re: Python Tooling
  In-Reply-To: <DL3EYFR4ZDXM.R13R00LPMM7T@partin.io>

* 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