So do you think we can release 3.2.9 with the old 3.2.8 code, or should
this block the release until we have a correct fix? I'm hoping we can do
a 3.3 release in October or November, FYI.
I don't think it is worth trying to work on a fix that makes new
FieldStorage code work with Trac. Just go with 3.2.8 FieldStorage code
in 3.2.9. In 3.3 then use new code with understanding that it will break
Trac.
I see this as acceptable as version of Trac in subversion trunk does
away with all the FieldStorage fiddles and instead they base it on a
WSGI wrapper which I presume therefore avoids use of FieldStorage.
We just need to ensure that this newer version of Trac is released
before we release mod_python 3.3 and that we notify them that older
versions of Trac will not work with mod_python 3.3 and people will need
to use their most latest version of Trac instead.
You have my +1 on that. Let's keep the 3.2.8 implementation for now, and do the rework in 3.3 in
cooperation with the Trac people.
Mike.
