I think the commit you want is 51f359d1252865181247e5182294ae5a28e3116d
The one you tried is the one the upstream maintainer originally thought
introduced the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
The upstream maintainer has already implemented a fix and tagged a new
release which I have tested as working. You were not wrong when you said
they were responsive! The version that includes the fix is 3.5.0.4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thank you Sergio, and you are welcome!
I have filed an upstream bug as you requested:
https://github.com/grisha/mod_python/issues/138
Thanks again,
Mike.
** Bug watch added: github.com/grisha/mod_python/issues #138
https://github.com/grisha/mod_python/issues/138
--
You received this bug not
Hello Lena,
Thank you for looking into this bug. I have created a minimal test case
that illustrates the problem and is completely independent of trac -
though it exposes the issue that causes trac to fail.
To install the test case:
1. Extract the attached archive python_bug_2078527.tar.gz into
Public bug reported:
Ubuntu version: 24.04.1
Package version: 3.5.0.1-3build1
Python version: 3.12.3
I encountered this problem after upgrading from jammy -> nobel and
installing Trac 1.6. I do not believe this is a problem with Trac
however.
The trac.web.modpython_frontend handler supplied by T
