| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
| Cc: | pgsql-www(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Upgrade some pgweb python dependencies |
| Date: | 2026-02-12 12:02:46 |
| Message-ID: | CABUevEyYnW63ai80m+X5884LADi6K4=VDeEpuVRC1N4cfe94Lg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Wed, 11 Feb 2026 at 23:40, Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com>
wrote:
> I submitted a patch to pgarchive recently, which led me to setting up
> pgweb, based on the instructions in docs/dev_install.rst.[0]
>
> Using debian 13 and python 3.9, I ran into several errors running `pip
> install -r requirements.txt`. The versions pinned there look quite
> old. The latest allowed version of pycryptodomex even seems to use
> python2 syntax, so I don't understand how it works for anyone else.
>
These requirements files are, ahem, badly maintained. I assume nobody
really uses them :/
FWIW, since you're on debian, the easiest is to just use the debian
packaged versions of basically everything. Our production is on debian
bookworm and testing is on debian trixie, so either of those should work.
The only thing you need to install from pip at this point is Django itself
and cvss (if you want the security pages).
Doesn't mean the requirements.txt shouldn't be better maintained, so we
should look at that, but as a quick-fix for your current situation and to
make sure you're running something that matches what's actually used in
production.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2026-02-12 12:05:02 | Re: Fill page when printing archived threads |
| Previous Message | Zbynek Vanzura | 2026-02-12 09:24:38 | Wiki editor request - – username Heptau |