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

[Bob Ippolito]

On Dec 10, 2004, at 2:17 AM, pythonmac at gisborne.emailuser.net wrote:

> 	From: 	  gisborne at emailuser.net
> 	Subject: 	Re: Pythonmac-SIG Digest, Vol 20, Issue 11
> 	Date: 	December 10, 2004 1:08:54 CST
> 	To: 	  pythonmac-sig at python.org
>
> Ran into some troubles with the below. Comments interspersed.
>
>> From: Robert Valsjö <robert at xtrafone.com>
>> Date: December 8, 2004 3:06:50 CST
>> To: PythonMac-sig at python.org
>> Cc: Subject: [Pythonmac-SIG] How-To upgrade Apples python 
>> installation in Mac OS X 10.3 from python 2.3 to 2.4
>>
>>
>> How to upgrade Apples python installation in Mac OS X 10.3 from 
>> python 2.3 to 2.4
>
> <snip>
>
>> >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.

>> 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.

-bob