[Pythonmac-SIG] Python 2.4.1 not replacing earlier versions.

Simon Brunning simon.brunning at gmail.com
Wed Aug 31 15:56:22 CEST 2005


On 8/30/05, Craig Amundsen <cdamundsen at gmail.com> wrote:
> The python you installed lives in /usr/local/bin. If you want it to
> run when you type 'python' at the prompt you need to make sure that
> /usr/local/bin is before /usr/bin in your path.

Or I can just invoke the /usr/local/bin version explicitly, yes? Seems
to work...

How do I specify that in a shebang line? I tried "#!/usr/local/bin
python", but I got a "bad interpreter: Permission denied" error
message.

> > Now, I can appreciate that changing the version of Python that the OS
> > uses might not be a good idea, but how do I get 2.4.1 working with
> > appscript and PyObjC? Or is that a bad idea?
> 
> When you build modules they are available to the version of python
> that built them. So if you build appscript (and its many dependencies)
> and PyObjC with 2.4.1, you'll be able to load them with 2.4.1.

As I thought.

> PS - Oh, and don't try to replace the Apple-supplied Python with a
> newer version. Down that path lies madness and reinstallation of the
> system. With proper attention, multiple versions of Python can live
> quite happily on the Mac.

Thanks. I won't do that, then. ;-)

-- 
Cheers,
Simon B,
simon at brunningonline.net,
http://www.brunningonline.net/simon/blog/


More information about the Pythonmac-SIG mailing list