Hi, while fighting with mod_python bugs it turns out at least one of them is in python itself. It was present since 2.3.5. The official bugfix is at http://sourceforge.net/tracker/index.php?func=detail&aid=1163563&group_id=5470&atid=105470 Please apply it soon to portage. It's very hard to isolate the problem for an ordinary mod_python user. But, it was actually reported Java Python and it's really a python bug. Thanks.
i agree this is critical too. we need to backport the patch from cvs. i'll have a go at it, but if someone else beats me to it, please attach it to this bug or commit to portage :)
Hi, mod_python-3.2.2b is out some days already. I Just did: # cp mod_python-3.1.4-r1.ebuild mod_python-3.2.2b.ebuild # ebuild mod_python-3.2.2b.ebuild digest # emerge =dev-python/mod_python-3.2.2b and it works fine for me. How about putting as stable for ~x86? ;) It is an excellent bugfix release!
Fixed in python-2.4.2 which is now stable.