2008/12/17 Reed O'Brien <[email protected]>: > A custom location and not a framework. One issue is that I don't understand > the Framework system apple uses very well. Another is that I develop > multiple apps with different versions of Python (and some with the same > version but different package needs) and I want them to link to specific > installations of python. > > I have found it easiest to just maintain builds of python for specific apps > (managed with zc.buildout) and link to them...
Not sure what the problem is. I install Python into separate locations and just make sure framework directory is under it. Eg for Python 3.0 used: ./configure --prefix=/usr/local/python-3.0 --enable-framework=/usr/local/python-3.0/frameworks --enable-universalsdk=/ MACOSX_DEPLOYMENT_TARGET=10.5 --with-universal-archs=all For Python 2.5.1 used: ./configure --prefix=/usr/local/python-2.5.1 --enable-framework=/usr/local/python-2.5.1/frameworks In that case hadn't enable building of all architectures thus why fewer options. The latter is same version number as OS supplied one, but don't have problem with conflicts. Also, if just the installed third party packages need to be different, aren't you using virtual environments. Thus would need to install base installation of specific version multiple times. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
