From: <sp...@ma...> - 2005-10-21 18:06:19
|
I was trying to get my test environment migrated from 1.3 to 2.0.3 while also switching from mod_python to Spyce standalone via mod_proxy and ran into some session issues. In order to better grasp the problem, I figured I should try and determine if the problem was switching from 1.3 to 2.0.3 that caused it -or- switching from mod_python to standlone caused it. So rather than changing two things at once, I then tried to use 2.0.3 with mod_python. The only differences in my httpd.conf file are: 1.3: <IfModule mod_python.c> AddHandler python-program .spy PythonHandler run_spyceModpy::spyceMain PythonPath "sys.path+[r'/usr/share/spyce']" PythonOption SPYCE_CONFIG "/var/www/html/spyce.conf" </IfModule> 2.0.3: <IfModule mod_python.c> AddHandler python-program .spy PythonHandler run_spyceModpy::spyceMain PythonPath "sys.path+[r'/usr/share/spyce-2.0.3']" PythonOption SPYCE_CONFIG "/usr/share/spyce-2.0.3/spyceconf.py" </IfModule> The 1.3 configuration works great. When I switch to the 2.0.3 configuration I receive mod_python import errors in the Apache error_log: PythonHandler run_spyceModpy::spyceMain: ImportError: No module named run_spyceModpy, referer: http://localhost:9876/test/ $ ls -l /usr/share/spyce-2.0.3/run_spyceModpy.py -rwxr-xr-x 1 apache apache 1515 Sep 10 2002 /usr/share/spyce-2.0.3/run_spyceModpy.py* I can't seem to find anything obviously wrong with my configuration. Perhaps I'm missing something basic (hopefully). I followed the usual steps from the end of the spyceApache.conf which worked for me in the past. Any ideas as to what is wrong with my mod_python/Spyce configuration for 2.0.3? Thanks, Phil |