[MacPorts] #18878: mod_python 3.3.1_1 "Target org.macports.activate returned: Not a directory"

[MacPorts]

#18878: mod_python 3.3.1_1 "Target org.macports.activate returned: Not a directory"
-------------------------------+--------------------------------------------
 Reporter:  francis@…          |       Owner:  macports-tickets@…                   
     Type:  defect             |      Status:  new                                  
 Priority:  Normal             |   Milestone:  Port Bugs                            
Component:  ports              |     Version:  1.7.0                                
 Keywords:                     |        Port:  mod_python                           
-------------------------------+--------------------------------------------

Comment(by francis@…):

 Replying to [ticket:18878 francis@…]:
 > After the error, some of the files (e.g.
 /opt/local/apache2/modules/mod_python.so) seem to have been created, but
 mod_python does not work - after adding "LoadModule python_module
 modules/mod_python.so" to http.conf and restarting apache2 I see the
 following error repeated in /opt/local/apache2/logs/error_log:

 I have just discovered that the apache crashes were being caused by
 mod_python.so being linked against the system Python 2.5 instead of the
 MacPorts python 2.4 because I hadn't done "sudo python_select python24" so
 the symlinks in /opt/local/Library/Frameworks/Python.framework weren't set
 up.  However, doing python_select did not fix the original "Not a
 directory" error and I have also encountered the "Not a directory" error
 on another machine.

-- 
Ticket URL: <http://trac.macports.org/ticket/18878#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS