An oddity of the PATH variable in Linux (or at least Ubuntu) is that there
is a folder in PATH called /home/~/bin. The ~ is replaced with your profile
name. If you create that folder and put the file into it, you can invoke it
from anywhere in the filesystem with just its name.
On Tue, May 24, 2
Hi Hank,
On 24 May 2011 15:15, Hank Wilkinson wrote:
> Yes, I would love to know why it doesn't work, or what I'm doing wrong.
>
> John-Wilkinsons-iMac:p31summerfield wilkinson$ cat hello.py
> #!/usr/bin/env python
>
> print("Hello world")
> John-Wilkinsons-iMac:p31summerfield wilkinson$ chmod +
Yes, I would love to know why it doesn't work, or what I'm doing wrong.
John-Wilkinsons-iMac:p31summerfield wilkinson$ cat hello.py
#!/usr/bin/env python
print("Hello world")
John-Wilkinsons-iMac:p31summerfield wilkinson$ chmod +X hello.py
John-Wilkinsons-iMac:p31summerfield wilkinson$ ./hello.py
On 24 May 2011 14:51, Hank Wilkinson wrote:
> Thank you, I changed the first line to:
> #!/usr/bin/env/python3
> then I tried again:
> John-Wilkinsons-iMac:p31summerfield wilkinson$ ./hello.py
> -bash: ./hello.py: /usr/bin/env/python3^M: bad interpreter: Not a directory
> John-Wilkinsons-iMac:p31
On 24 May 2011 14:53, Hank Wilkinson wrote:
> Thank you.
> John-Wilkinsons-iMac:p31summerfield wilkinson$ which python
> /opt/local/bin/python
>
> OK excellent.So you can either use '#!/opt/local/bin/python' in your
script, or alternatively '/usr/bin/env python' (presuming that you have
'env'
Thank you.
John-Wilkinsons-iMac:p31summerfield wilkinson$ which python
/opt/local/bin/python
On May 24, 2011, at 9:27 AM, Walter Prins wrote:
> The problem likely is as intimated by the error message that your python
> interpreter not called "/usr/local/bin/python3.1" but I'd offhand guess,
>
to...
>
> #!/usr/local/bin/python3
>
> ...you should get along much better! :)
>
> S.
>
> -Original Message-
> From: Hank Wilkinson [mailto:hwilkin...@triad.rr.com]
> Sent: Tuesday, May 24, 2011 2:25 PM
> To: Flynn, Stephen (L & P - IT)
> Cc: t
Hank Wilkinson wrote:
> I am trying to do script in python using "./"
> Here is a session showing "bad interpreter: No such file or directory"
> Is this a python question/problem?
It's a bash problem. The shell cannot cope with Windows line endings: ^M in
the error message stands for chr(13) or
On 2011/05/24 03:10 PM, Hank Wilkinson wrote:
I am trying to do script in python using "./"
Here is a session showing "bad interpreter: No such file or directory"
Is this a python question/problem?
Last login: Sat May 21 14:22:49 on ttys000
John-Wilkinsons-iMac:~ wilkinson$ cd
/Users/wilkinson/
From: Hank Wilkinson [mailto:hwilkin...@triad.rr.com]
Sent: Tuesday, May 24, 2011 2:25 PM
To: Flynn, Stephen (L & P - IT)
Cc: tutor@python.org
Subject: Re: [Tutor] python scripting using "./"
John-Wilkinsons-iMac:p31summerfield wilkinson$ ls -al
/usr/local/bin/python
ls: /usr
On Tue, May 24, 2011 at 9:10 AM, Hank Wilkinson wrote:
> I am trying to do script in python using "./"
> Here is a session showing "bad interpreter: No such file or directory"
> Is this a python question/problem?
>
> Last login: Sat May 21 14:22:49 on ttys000
> John-Wilkinsons-iMac:~ wilkinson$ cd
John-Wilkinsons-iMac:p31summerfield wilkinson$ ls -al /usr/local/bin/python
ls: /usr/local/bin/python: No such file or directory
John-Wilkinsons-iMac:p31summerfield wilkinson$ ls -al /usr/local/bin/python3
lrwxr-xr-x 1 root wheel 69 Mar 21 13:45 /usr/local/bin/python3 ->
../../../Library/Framew
Here is what you asked me:
John-Wilkinsons-iMac:p31summerfield wilkinson$ ls -al /usr/local/bin/pytho*
lrwxr-xr-x 1 root wheel 69 Mar 21 13:45 /usr/local/bin/python3 ->
../../../Library/Frameworks/Python.framework/Versions/3.1/bin/python3
lrwxr-xr-x 1 root wheel 76 Mar 21 13:45 /usr/local/bi
The problem likely is as intimated by the error message that your python
interpreter not called "/usr/local/bin/python3.1" but I'd offhand guess,
probably "/usr/local/bin/python". (Indeed, you run the interpreter yourself
as "python" not "python3.1" so you should not be using "python3.1" in your
s
What is your Python executable called? You refer to it as "python" on
the command line but your "#!" line in your script refers to the
executable as "python3.1". tried it with just "python" in the #! Line?
Check the output of 'ls -al /usr/local/bin/pytho*'...
S.
-Original Message-
From:
15 matches
Mail list logo