[Guido asked me to file this as an issue.] On Mac OS X Apple has configured the system provided Python to also search this global site-packages directory: /Library/Python//site-packages/ This allows users to install their own system-wide packages there (and not have them to drop into /System/Library/Frameworks/Python....../). Unfortunately if you install Python from python.org (or pythonmac.org) it is not searching this path, it only searches the site-packages directory _within_ its own framework: /Library/Frameworks/Python...../ That directory is of course not searched by the Apple provided Python. This is an issue for addon package installers (think PIL or numpy): There is no single path that will be found by both the system provided Python and a Python installed from python.org. This makes most/all (?) of the pre-built packages on pythonmac.org unusable with the version of Python Apple ships although there is no version conflict or such - it simply installs stuff in the "wrong" directories. Many people who tried to install PIL for Django or App Engine stumbled into this. The system provided Python version was fine. But compiling PIL is hard. So they installed PIL from pythonmac.org. That couldn't be found by Python. Now some people manually copied stuff around, some created symlinks, some installed a second Python 2.5. (The lucky ones picked a Python download from python.org, the not so lucky ones installed the 2.5.0 release from pythonmac.org...) I've attached a diff of a stock Python 2.5.1 library against what I found on my Apple Mac OS X 10.5 (Leopard) system. I've dropped changes that are not related to the path.
IIUC, you are not the author of the patch (in the sense that you wrote the new code), but rather created a diff between Apple's code and Python's. In this case, we cannot accept the patch - it needs to be contributed by the authors (i.e. Apple). Furthermore, I fail to see how this patch can affect the places were Python searches for site-packages - it only deals with Python code that might need adjustment if Python would search in this other location. Please correct me if I'm wrong.
Sorry, I should have made this clear: I am NOT proposing to add this patch. I meant this more to show what related changes were done by Apple. Some of these clearly wouldn't even work like this if applied to a Python not installed in /System/Library/Frameworks/... IMHO the most interesting piece of that diff is the change to site.py which makes it look into /Library/Python/
I'm in favour of adding /Library/Python/x.y/ to sys.path for Python 2.7 and 3.1 and will work on that during the Pycon sprints. /Library/Python will be added after the site-packages directory inside the framework instead of replacing the latter directory. The reason for this is that we don't want to install all packages in a location that's visible to Apple's copy of Python because you could accidently replace packages that Apple ships as part of the "Extras" directory that way. Replacing those is bad because those libraries are used by Apple system software and replacing stuff might therefore break the system (particularly on server systems). I won't backport to 2.6 and 3.0 because this is a feature request and not a bugfix. W.r.t. building PIL and other extensions: we've had a discussion about this during the startup phase of the macpython-sig sprint and we have some ideas to make this situation less painful in the future (without necessarily having to patch Python for that).
