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

2005-09-02 Thread Trent Mick
[Bob Ippolito wrote] > Of course the standard installers make this link. What they are > missing (the framework ones anyway) is a link for pydoc, ActivePython installs a /usr/local/bin/pydoc... > and all of > them are missing a versioned pydoc binary. ...but not a versioned one. Trent

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

2005-09-02 Thread Chris Barker
Bob Ippolito wrote: >> I really wish specifying the version would become standard practice in >> python development. > > That cuts both ways, for a lot of scripts you don't give a damn which > python it is and changing the hash-bang every time you upgrade is a pain. True. I actually make a cho

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

2005-09-02 Thread Bob Ippolito
On Sep 2, 2005, at 2:52 PM, Chris Barker wrote: > Just to add my $0.02 for completeness: > > I think the standard installers put a "python2.4" as well as "python" > in usr/local/bin. If they don't, they should, and until then, you can > put in a link yourself: Of course the standard installers

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

2005-09-02 Thread Chris Barker
Just to add my $0.02 for completeness: People use: #!/usr/bin/env python so that the script will work on any system with a python on the PATH, whether it's in /usr/bin or /usr/local/bin or wherever else. Particularly on Linux systems, python gets installed different places depending on whethe

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

2005-09-01 Thread Simon Brunning
On 8/31/05, Robert Kern <[EMAIL PROTECTED]> wrote: > It selects the first executable named "python" in the PATH. The shebang > line requires an explicit executable. For example, Thanks, All. I've got it all working now, with your help. I'm glad to see that the Python Mac community is as beyond-the

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

2005-08-31 Thread Robert Kern
Kevin Dangoor wrote: > #!/usr/bin/env python > > is actually saying to invoke the "env" command (you can type 'man env' > to see what that command's all about). This particular usage of env > does not actually do anything of value, as far as I can see. It selects the first executable named "pyth

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

2005-08-31 Thread Kevin Dangoor
On 8/31/05, Simon Brunning <[EMAIL PROTECTED]> wrote: > On 8/31/05, Craig Amundsen <[EMAIL PROTECTED]> wrote: > > Did you mean #! /usr/local/bin/python > > or #! /usr/local/bin python ? > > I meant the latter - the first version works for me too. Thanks. > > I extrapolated "#! /u

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

2005-08-31 Thread Simon Brunning
On 8/31/05, Craig Amundsen <[EMAIL PROTECTED]> wrote: > > 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.

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

2005-08-31 Thread Craig Amundsen
Hi - > 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. Did you mean #! /usr/local/bin/python or

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

2005-08-31 Thread Simon Brunning
On 8/30/05, Craig Amundsen <[EMAIL PROTECTED]> 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 explic

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

2005-08-31 Thread Simon Brunning
On 8/30/05, Bob Ippolito <[EMAIL PROTECTED]> wrote: > I think that installer is broken, compile from source. > appscript does not have an installer for 2.4, you'll have to compile > it and its 5 or 6 dependencies. Thanks. I've grabbed source copies of all of these, and I'll have a bash with them t

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

2005-08-30 Thread Craig Amundsen
Hi - On 8/30/05, Simon Brunning <[EMAIL PROTECTED]> wrote: > I think that may be something to do with the fact that the original > version of Python that came with the machine is still 'in charge'. > Starting Python on the command line gives me version 2.3.5 - and when > I installed appscript, it

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

2005-08-30 Thread Bob Ippolito
On Aug 30, 2005, at 9:53 AM, Simon Brunning wrote: > Complete and utter Mac newbie here - be gentle with me! > > Hi, all. I've downloaded and installed MacPython 2.4.1 from > undefined.org. It installed happily enough, and seems to run fine. But > when I attempt to install PyObjC (from > pyobjc-1

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

2005-08-30 Thread Simon Brunning
Complete and utter Mac newbie here - be gentle with me! Hi, all. I've downloaded and installed MacPython 2.4.1 from undefined.org. It installed happily enough, and seems to run fine. But when I attempt to install PyObjC (from pyobjc-1.3.7-py2.4-macosx10.4.zip) it says that it requires Python 2.4.