On 16/02/06, David Rock <[EMAIL PROTECTED]> wrote:
The whole idea was to use a path where there was nothing just to prove you don't get the ^M on all errors of that type.
* Adam <[EMAIL PROTECTED]> [2006-02-16 14:23]:
> On 16/02/06, Brian van den Broek <[EMAIL PROTECTED]> wrote:
>
> It seems to me that that ^M is your problem although I'm not quite sure
> where it came from there seems to be an extra character on the end of the
> copied one. Here's a little test I did:
> <code>
> #! /bin/py
> print "What the hell!!"
> </code>
> [EMAIL PROTECTED]:~$ ./test.py
> -bash: ./test.py: /bin/py: bad interpreter: No such file or directory
> and there doesn't seem to be any weird thing on the end even though that
> file doesn't exist.
I would verify that /bin/py is the actual location of your python
interperter. That's a really weird location.
The whole idea was to use a path where there was nothing just to prove you don't get the ^M on all errors of that type.
_______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor
