Re: Status of mod_python 3.3.

2006-10-19 Thread Graham Dumpleton
Jim Gallacher wrote .. > # Populate FieldStorage with the original query string > parameters, if > # they aren't already defined through the request body > if req.args: > qsargs = [] > for pair in util.parse_qsl(req.args, 1): >

Re: Status of mod_python 3.3.

2006-10-19 Thread Jim Gallacher
Graham Dumpleton wrote: Jim Gallacher wrote .. Graham Dumpleton wrote: On JIRA, the following issues are still marked as incomplete for mod_python version 3.3. I have noted my own comments about where they are up to and what I think still needs to be done. MODPYTHON-93 Improve util.FieldStor

Re: Status of mod_python 3.3.

2006-10-19 Thread Mike Looijmans
Graham Dumpleton wrote: ... MODPYTHON-93 Improve util.FieldStorage efficiency. This was actually marked as resolved but reopened because it was discovered that changes meant that Trac <=0.9.6 would no longer work. The changes were also backed out of mod_python 3.2.X branch and not released in 3.

Re: Status of mod_python 3.3.

2006-10-19 Thread Jim Gallacher
Graham Dumpleton wrote: On JIRA, the following issues are still marked as incomplete for mod_python version 3.3. I have noted my own comments about where they are up to and what I think still needs to be done. MODPYTHON-93 Improve util.FieldStorage efficiency. This was actually marked as resolv

[jira] Closed: (MODPYTHON-53) Show link for subversion and JIRA on www.mod_python website

2006-10-19 Thread Jim Gallacher (JIRA)
[ http://issues.apache.org/jira/browse/MODPYTHON-53?page=all ] Jim Gallacher closed MODPYTHON-53. -- > Show link for subversion and JIRA on www.mod_python website > --- > > Key: MODPYTHON

[jira] Resolved: (MODPYTHON-53) Show link for subversion and JIRA on www.mod_python website

2006-10-19 Thread Jim Gallacher (JIRA)
[ http://issues.apache.org/jira/browse/MODPYTHON-53?page=all ] Jim Gallacher resolved MODPYTHON-53. Resolution: Fixed > Show link for subversion and JIRA on www.mod_python website > --- > >

Re: two mod_python leaks

2006-10-19 Thread Jeff Robbins
Yes regarding placement of PyThreadState_Clear...sorry about that. I rebuilt and ran my simple test and it shows no leaks. static void release_interpreter(void) { PyThreadState *tstate = PyThreadState_Get(); // JSR PyThreadState_Clear(tstate); #ifdef WITH_THREAD PyEval_ReleaseThread(tstate); #

Re: two mod_python leaks

2006-10-19 Thread Graham Dumpleton
Comments below. On 19/10/2006, at 8:55 PM, Graham Dumpleton wrote: For such issues, by all means just send the email direct to the mailing list. I have copied this back onto the list and I'll do some research into what you describe. BTW, I don't use Windows, but there are others on the lis

Re: two mod_python leaks

2006-10-19 Thread Graham Dumpleton
For such issues, by all means just send the email direct to the mailing list. I have copied this back onto the list and I'll do some research into what you describe. BTW, I don't use Windows, but there are others on the list who do and it may help if you can explain what methodology you are u