/System/Library vs /Library

Just so hopefully nobody else hits this problem.

If you have a system that started life as a 10.2 system with python 
added on, upgraded to 10.3 and run an application that embeds/links 
to Python.framework, things might not work as expected.

The 10.2 add-on python gets installed in 
/Library/Frameworks/Python.framework.  10.3 provides 
/System/Library/Frameworks/Python.framework.  If your app is linked 
to Python.framework, it will end up with the 10.2 version of 
Python.framework, and not the 10.3 one, since /Library/Frameworks is 
searched before /System/Library/Frameworks (see 
http://developer.apple.com/documentation/MacOSX/Conceptual/BPFrameworks/Tasks/InstallingFrameworks.html#//apple_ref/doc/uid/20002261/TPXREF101).

Even though both of these probably are 2.3 python, if you use PackMan 
in SLFP to install a module (say, PyObjC), your app that embedded 
Python via Python.framework won't see it, since it will end up 
looking in LFP.  You will then swear, remove things, re-install 
things, try to figure out why system.path on the /usr/bin/python 
works correctly (and refers to the site package in SLFP where you 
just installed PyObjC), yet your app is unable to import something 
you know that you just installed.


--
Glenn Andreas                      gandreas@xxxxxxxxxxxx
mondo blobbo, Cythera, Theldrow, oh my!
Mad, Bad, and Dangerous to Know

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIG@xxxxxxxxxx
http://mail.python.org/mailman/listinfo/pythonmac-sig