[Pythonmac-SIG] How-To upgrade Apples python installation in Mac OS X 10.3 from python 2.3 to 2.4

[pythonmac at gisborne.emailuser.net]

> From: Bob Ippolito <bob at redivi.com>
> Date: December 10, 2004 1:29:53 CST
> To: pythonmac at gisborne.emailuser.net
> Cc: pythonmac-sig at python.org
> Subject: Re: [Pythonmac-SIG] Re: How-To upgrade Apples python 
> installation in Mac OS X 10.3 from python 2.3 to 2.4
>>> >make
>>> >make frameworkinstall
>>
>> make frameworkinstall
>> pbxcp: error: open(): 
>> ///Applications/MacPython-2.4/PythonLauncher.app/Contents/Info.plist: 
>> Permission denied
>> ...failed PBXCp 
>> ///Applications/MacPython-2.4/PythonLauncher.app/Contents/Info.plist 
>> ...
>> ** BUILD FAILED **
>> make[1]: *** [install_PythonLauncher] Error 1
>> make: *** [frameworkinstallapps] Error 2
>>
>> Fine: I did sudo make frameworkinstall, which executes without error.
>>
>>> >make frameworkinstallextras
>>
>> Same privileges complaint; same solution.
>
> Everything in the /Applications folder should be writable by anyone in 
> the admin group, so your configuration is to blame here, not the 
> instructions.  Some package you installed probably had bad 
> permissions...  This should work for most systems.
>
> If you open up Disk Utility, there is a button that will repair 
> permissions on a volume.  With correct permissions, these steps 
> should've succeeded.  Given this error, you should probably do it.

I know this is somewhat off-topic, but I ran repair permissions using 
Disk Utility, and then manually went in and did chmod on both Contents 
and Info.plist so that both owner (root) and group (wheel) could rwx 
and rw the folder and file, respectively.

I still get the permission error shown above. Weird, huh?

>
>>> Change you PATH:
>>>
>>> >emacs ~/.bashrc
>>>
>>> Add:
>>>
>>> PATH=/usr/local/bin:$PATH
>>> export PATH
>>
>> OK. Then I do:
>>
>> python
>> Python 2.3 (#1, Sep 13 2003, 00:49:11)
>> [GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] on darwin
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>>
>
> You also need to set the PATH from the shell prompt, or start a new 
> terminal window.  Editing .bashrc doesn't do anything to a currently 
> running bash process.

Works now, but only after having run the two latter makes as root. I 
hope that won't cause problems.

Thanks for your help.

Guyren G Howe