[
http://issues.apache.org/jira/browse/MODPYTHON-143?page=comments#action_12443385
]
Graham Dumpleton commented on MODPYTHON-143:
Still need to update new module importer code so as to log exceptions which
might occur in
[
http://issues.apache.org/jira/browse/MODPYTHON-143?page=comments#action_12427741
]
Graham Dumpleton commented on MODPYTHON-143:
An issue which still needs to be looked at with new module importer is that for
historical reasons,
[
http://issues.apache.org/jira/browse/MODPYTHON-143?page=comments#action_12427684
]
Graham Dumpleton commented on MODPYTHON-143:
This issue is basically complete and is just lacking some documentation.
The name of the PythonOption
[
http://issues.apache.org/jira/browse/MODPYTHON-143?page=comments#action_12423617
]
Graham Dumpleton commented on MODPYTHON-143:
As per previous comments in:
http://www.modpython.org/pipermail/mod_python/2006-May/021095.html
[
http://issues.apache.org/jira/browse/MODPYTHON-143?page=comments#action_12376144
]
Graham Dumpleton commented on MODPYTHON-143:
Going to be a pain and change the name of the PythonOption used to enable the
new importer. The reason for this
[
http://issues.apache.org/jira/browse/MODPYTHON-143?page=comments#action_12371067
]
Graham Dumpleton commented on MODPYTHON-143:
New importer commited.
Note that if you wish to run the test suite using the new importer, you need to
edit
[
http://issues.apache.org/jira/browse/MODPYTHON-143?page=comments#action_12370976
]
Graham Dumpleton commented on MODPYTHON-143:
For technical reasons related to ensuring new importer got to take over from
old at the right time, original plan
