Graham Dumpleton
graham.dumpleton at gmail.com
Sun Jun 13 09:26:58 EDT 2010
On 12 June 2010 09:04, Patrick May <patrick at mammalfish.com> wrote: > Hello, > I have a python web application which requires python2.5. I am attempting > to compile mod_python on Snow Leopard against the OS apache and the OS > python2.5. The steps I have taken are as follows: > 1. checked out mod_python from svn > $ svn co https://svn.apache.org/repos/asf/quetzalcoatl/mod_python/trunk > mod_python-svn > 2. configured mod_python to use the Snow Leopard Apache and the Snow Leopard > python2.5 > $ cd mod_python-svn > $ ./configure --with-apxs=/usr/sbin/apxs --with-python=/usr/bin/python2.5 > 3. built mod_python > $ make > The resulting mod_python.so is linked against the 2.6 framework: > $ otool -L src/mod_python.so > src/mod_python.so: > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version > 125.0.1) > /System/Library/Frameworks/Python.framework/Versions/2.6/Python > (compatibility version 2.6.0, current version 2.6.1) > This is essentially broken for my purposes. If I continue the process and > install, it becomes apparent that mod_python is indeed running the 2.6 > interpreter and my application does not run. I have seen some conversation > about this issue, but those conversations did not appear productive. > Is 2.5 simply not supported? Is this a known bug on mac os x? Are there > any suggestions for remedying the situation? This is exactly the outstanding problem I mention in relation to MacOS X in: http://blog.dscpl.com.au/2010/05/modpython-project-soon-to-be-officially.html The question at this point is why must you use mod_python? Graham
|