Package: python3-webpy
Version: 1:0.62-6
Followup-For: Bug #1087177
Dear Maintainer,
* What led up to the situation?
Upgrading to a newer version of web.py (possibly newer version of
python3 at the same time) broke an existing website
* What exactly did you do (or not do) that was effective (or
ineffective)?
Just displaying a page rendered from a template.
* What was the outcome of this action?
The page rendering catastrophically fails, leaving juat an "internal
server error" page
* What outcome did you expect instead?
The page to display normally
I suspect this is to do with the new escaping rules in python. It might be as
simple as making the djangoerror_t string a raw string.
-- System Information:
Debian Release: 13.5
APT prefers stable
APT policy: (900, 'stable'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'stable-debug')
Architecture: arm64 (aarch64)
Kernel: Linux 5.10.0-34-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-webpy depends on:
ii python3 3.13.5-1
ii python3-cheroot 10.0.1+ds1-4
ii python3-legacy-cgi 2.6.3-1
Versions of packages python3-webpy recommends:
ii python3-mysqldb 1.4.6-2+b6
python3-webpy suggests no packages.
-- no debconf information
