Graham Dumpleton wrote: > Sorry for the flurry of JIRA emails on the list, but I have been doing > some housework > and drawn a line in the sand in respect of what I see as the remaining > tasks that > should be attempted for mod_python 3.3. These are: > > MODPYTHON-109 Signal handler calling Py_Finalize() when child processes > being killed. > MODPYTHON-127 Use namespace for mod_python PythonOption settings. > MODPYTHON-159 multiline headers in multipart/form not handled > MODPYTHON-128 Have assigning req.filename automatically update req.finfo. > MODPYTHON-182 Memory leak in request readline() > MODPYTHON-180 publisher wrongly generating warning that there is > 'nothing to publish' > MODPYTHON-93 Improve util.FieldStorage efficiency > MODPYTHON-59 Add get_session() method to request object I think this ill-fated bit of code should be purged and the issue closed. It's in there but just raises a NotImplemented exception. I've not done any work on moving it forward and I think it's sloppy to leave it in the code base.
There is also the apache.table() memory leak, but not reported in JIRA yet. I'll go do that right now. > You can see the actual details by going to: > > http://issues.apache.org/jira/browse/MODPYTHON > > and click on the link for items scheduled for 3.3. In that list you will > also see: > > MODPYTHON-63 Handle wildcard in Directory to sys.path transfer > MODPYTHON-104 Allow Python code callouts with mod_include (SSI). > MODPYTHON-143 Implement and integrate a new module importer. > > These haven't been marked as resolved yet, but work has been done. Minor > tweaks > may still need to be done on new importer, plus it may now also be made > the default > for mod_python 3.3 where wasn't necessarily expecting that to be the > case up till > now. Documentation for SSI and new importer also need to be done and in > the case > of SSI is the only reason it hasn't been marked as resolved. > > For those who are interested, please go through all the other > open/reopened items and > see if there is anything else you would especially like to see make it > into 3.3 and we can > have a look at what is involved and see whether we want to attempt to do > it or not. > > In respect of above, if someone other than the core developers would > like to volunteer > to come up with an updated patch for MODPYTHON-159 that would be great. > Other > than that everything else is probably in hand, although some feedback on > MODPYTHON-127 > in respect to how to nicely migrate from old option naming to new would > help. > > Thanks in advance. > > Graham >
