Re: Python Tooling

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)