[ http://issues.apache.org/jira/browse/MODPYTHON-167?page=all ]
Graham Dumpleton resolved MODPYTHON-167:
Fix Version: 3.3
Resolution: Fixed
> If PythonDebug is On and error occurs, status is 200 when it should really be
> 500.
> --
On 4/22/06, Graham Dumpleton <[EMAIL PROTECTED]> wrote:
> Unfortunately it tends to be just you and I tossing ideas back and forth
> and when you have a two person democracy at work, hard to get some
> consensus of what is the best direction to go. :-(
I think the namespace direction you're taking
[
http://issues.apache.org/jira/browse/MODPYTHON-127?page=comments#action_12376137
]
Graham Dumpleton commented on MODPYTHON-127:
Okay, lets not use camel case and where a sub namespace is required, it should
refer to the concept of what is bei
[
http://issues.apache.org/jira/browse/MODPYTHON-154?page=comments#action_12376138
]
Graham Dumpleton commented on MODPYTHON-154:
What I have decided to do here is by default not allow the new importer to look
back in the handler root directory
[
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 is
[ http://issues.apache.org/jira/browse/MODPYTHON-154?page=all ]
Graham Dumpleton resolved MODPYTHON-154:
Fix Version: 3.3
Resolution: Fixed
Finally decided on using option name "mod_python.importer.search_handler_root".
Setting PythonP
[ http://issues.apache.org/jira/browse/MODPYTHON-156?page=all ]
Work on MODPYTHON-156 started by Graham Dumpleton
> Module imports from server side includes and new importer.
> --
>
> Key: MODPYTHON-156
> URL: htt
