Re: Python Tooling

On Mon, 31 Aug 2026 at 22:23, Tristan Partin <tristan(at)partin(dot)io> wrote:

> 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:
> >> - 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?
>

Correct. The only things we're currently pulling from python reqiurements
is django itself (and the associated asgiref) and the cvss package (which
is not available on Debian).

> 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.
>

Yeah, that would definitely be an improvement :)

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>