[Pythonmac-SIG] Private frameworks - BINGO!

[Tony Lownds]

>Unfortunately it doesn't necessarily solve the problem we're looking 
>at: installing the whole bunch in a random location. The reason is 
>that we have a number of programs that refer to the framework: 
>PythonIDE.app, PythonLauncher.app (although it currently has a 
>hardcoded path it could link against the framework, even if only to 
>obtain it's pathname) and the hidden Python.app. And then there's 
>the python commandline tool, also hidden inside the framework at the 
>moment.

The shared modules in lib-dynload also refer back to the framework. 
When trying things out do an "import array"...

>We could solve this be sprinkling symlinks all over the place, but 
>I'm not sure I like that....

Maybe a small launcher program could find the Python.app bundle - 
perhaps using CFBundleGetBundleWithIdentifier("org.python.Python") - 
then augment DYLD_FRAMEWORK_PATH and finally exec the Python 
executable in the Python.app bundle.

Here is perhaps another reason to try to make something like this 
work: when I upgraded to Jaguar, it cleared out the 
/Library/Frameworks directory and Python.framework was "archived" in 
/Previous Systems

I see Bob already posted something about DYLD_FRAMEWORK_PATH :)

-Tony