Graham Dumpleton (JIRA) wrote:
[ http://issues.apache.org/jira/browse/MODPYTHON-158?page=comments#action_12373817 ]
Graham Dumpleton commented on MODPYTHON-158:
--------------------------------------------
With "__file__" output, last case now looks like:
[Mon Apr 10 16:29:09 2006] [error] make_obcallback: could not call init.\n
TypeError: init() takes no arguments (2 given)
[Mon Apr 10 16:29:09 2006] [error] make_obcallback: mod_python version mismatch,
expected '3.3.0-dev-20060410', found '<unknown>'.
[Mon Apr 10 16:29:09 2006] [error] make_obcallback: mod_python modules location
'/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/mod_python/__init__.pyc'.
[Mon Apr 10 16:29:09 2006] [error] get_interpreter: no interpreter callback
found.
[Mon Apr 10 16:29:09 2006] [error] [client 127.0.0.1] python_handler: Can't
get/create interpreter.
All this output should hopefully eliminate a lot of issues down the track.
Do we want to look at backporting these changes to 3.2.9????
+1
I think it would be helpful to get this out there as quickly as
possible. Sorting out these configuration issues is *boring* for us, and
frustrating for everyone.
My one concern is that there is a fair amount of new code being
introduced to support this feature, and there is no way to do any unit
testing. Let's make sure we do a careful code review if we decide to
push these changes into 3.2.9.
WRT to 3.2.9, I've been bogged down with other stuff and will likely be
fairly busy this week as well. How be we aim for a release somewhere
around April 22? I'd like to sort out why the apache 2.2 auth test fails
on some platforms before the release. It's a defect in the test I'm
sure, but I don't think we should make a release when failing tests.
Jim
