Hi Thomas,
It seems that you've cleanly killed the Apple-installed Python, which isn't too bad a thing after all. What I can suggest you do is this... Copy the entire /System/Library/Frameworks/Python.framework directory from someone and drop it into your system (same place of course). I will not suggest installing Python 2.4.1 until the Apple-installed Python is sorted out. My reasons being,
1. I have no idea what Mac OSX uses Python for. Although symlink may get you through most of the time but I cannot be sure that none of OSX's stuffs are hardcoded to use the Python in /System/Library/Frameworks/Python.framework.
I believe Apple only uses it for their fax utilities. There's also the CoreGraphics wrapper (which the fax stuff uses), but that's pretty useless as it is.
2. Installing another Python may or may not be a precise remedy. It may just worsen things and I won't want to bet on that.
The 2.4.1 build by Bob Ippolito is designed to work alongside the system-installed Python. It certainly won't replace it, but it shouldn't worsen anything.
3. Apple-installed Python's command line tools are symlinked from /usr/bin to /System/Library/Frameworks/Python.framework but the OSX installer for Python 2.4.1 places the commandline tools in /usr/local/bin and symlinked to /Library/Frameworks/Python.framework. So it seems to me that Python 2.4.1 (installed using OSX installer for Python 2.4.1) is not a precise replacement of Apple-installed Python...
Bingo. It's not intended to be one.
-- Robert Kern [EMAIL PROTECTED]
"In the fields of hell where the grass grows high Are the graves of dreams allowed to die." -- Richard Harter
-- http://mail.python.org/mailman/listinfo/python-list
