Re: Python Tooling

On Mon Aug 17, 2026 at 4:24 PM UTC, Magnus Hagander wrote:
> On Mon, 17 Aug 2026 at 18:13, Tristan Partin <tristan(at)partin(dot)io> wrote:
>
>> If I spent some time to improve the Python tooling for pgweb, would it
>> be accepted? Thinks we could do:
>>
>> - Add Python typing and type checking
>>
>
> That would be very useful I think.

Noted.

>> - Add linter checks
>>
>
> That may or may not be useful depending on exactly what it is :) But
> probably.

I'll see what this could look like.

>> - Use pyproject.toml
>> - Update dependencies
>>
>> Additionally, I would like to understand how people actually develop
>> this repo. `pip install -r requirements.txt` doesn't work for me because
>> my Python 3.11 toolchain cannot compile the version of psycopg that we
>> pin. Python 3.11 is what is recommended in the docs.
>>
>>
> 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?

> But unfortunately, we (which mostly means me) are very bad at keeping them
> up to date. Because for example Debian Trixie is on python 3.13, not 3.11.
> And since our currently existing tests are literally just "passes
> pycodestyle", it wouldn't catch that (and those tests pass on both 3.11 and
> 3.13).

Maybe we can change that.

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