Re: Unusual Python interpreter problem with os.fork()

2009-03-06 Thread DLitgo
On Mar 6, 7:20 am, Jean-Paul Calderone wrote: > On Fri, 6 Mar 2009 05:00:03 -0800 (PST), DLitgo wrote: > >Hello everyone, > > >I have a curious problem which I'm wondering if anyone here can shed > >some light on. I'm basically just following along with a guide which > >is going through some of t

Re: Unusual Python interpreter problem with os.fork()

2009-03-06 Thread Jean-Paul Calderone
On Fri, 6 Mar 2009 05:00:03 -0800 (PST), DLitgo wrote: Hello everyone, I have a curious problem which I'm wondering if anyone here can shed some light on. I'm basically just following along with a guide which is going through some of the os module, and I'm running some examples in the python in

Unusual Python interpreter problem with os.fork()

2009-03-06 Thread DLitgo
Hello everyone, I have a curious problem which I'm wondering if anyone here can shed some light on. I'm basically just following along with a guide which is going through some of the os module, and I'm running some examples in the python interpreter on mac os x (accessed through terminal/ bash).

Re: Interpreter problem

2005-04-08 Thread rbt
Steve Holden wrote: rbt wrote: Steve Holden wrote: rbt wrote: Steve Holden wrote: Greg Lindstrom wrote: I am using python 2.3.5 on a Linux system and have an odd problem dealing with the 'sha-bang' line. I have a file, driver.py which starts with #!/usr/bin/python and works fine (that is, when

Re: Interpreter problem

2005-04-08 Thread Ivan Van Laningham
Hi All-- Steve Holden wrote: > > > It's odd that deleting the line and reentering it on the Linux box did > > not correct the problem. Perhaps vim recognized the format as having > > cr-lf and inserted it even though I was editing on Linux. > > > > Anyhow, it would have been a long time before I

Re: Interpreter problem

2005-04-08 Thread Steve Holden
tuba_ranger wrote: Yes! I moved the file (which I had created on a windows box using a mounted drive), created a new one on the Linux box, typed in the shabang in Linux, then copied the old file (sans shabang) to the new file. It runs like a champ. My sysadmin suggests we run all of our files th

Re: Interpreter problem

2005-04-08 Thread Steve Holden
rbt wrote: Steve Holden wrote: rbt wrote: Steve Holden wrote: Greg Lindstrom wrote: I am using python 2.3.5 on a Linux system and have an odd problem dealing with the 'sha-bang' line. I have a file, driver.py which starts with #!/usr/bin/python and works fine (that is, when I type in ./driver.p

Re: Interpreter problem

2005-04-08 Thread rbt
Steve Holden wrote: rbt wrote: Steve Holden wrote: Greg Lindstrom wrote: I am using python 2.3.5 on a Linux system and have an odd problem dealing with the 'sha-bang' line. I have a file, driver.py which starts with #!/usr/bin/python and works fine (that is, when I type in ./driver.py at the co

Re: Interpreter problem

2005-04-08 Thread tuba_ranger
Yes! I moved the file (which I had created on a windows box using a mounted drive), created a new one on the Linux box, typed in the shabang in Linux, then copied the old file (sans shabang) to the new file. It runs like a champ. My sysadmin suggests we run all of our files through dos2unix befo

Re: Interpreter problem

2005-04-08 Thread Steve Holden
rbt wrote: Steve Holden wrote: Greg Lindstrom wrote: I am using python 2.3.5 on a Linux system and have an odd problem dealing with the 'sha-bang' line. I have a file, driver.py which starts with #!/usr/bin/python and works fine (that is, when I type in ./driver.py at the command prompt the fi

Re: Interpreter problem

2005-04-08 Thread rbt
Steve Holden wrote: Greg Lindstrom wrote: I am using python 2.3.5 on a Linux system and have an odd problem dealing with the 'sha-bang' line. I have a file, driver.py which starts with #!/usr/bin/python and works fine (that is, when I type in ./driver.py at the command prompt the file runs as

Re: Interpreter problem

2005-04-08 Thread Ruud de Jong
Greg Lindstrom schreef: I am using python 2.3.5 on a Linux system and have an odd problem dealing with the 'sha-bang' line. I have a file, driver.py which starts with #!/usr/bin/python and works fine (that is, when I type in ./driver.py at the command prompt the file runs as expected). I have

Re: Interpreter problem

2005-04-08 Thread Steve Holden
Greg Lindstrom wrote: I am using python 2.3.5 on a Linux system and have an odd problem dealing with the 'sha-bang' line. I have a file, driver.py which starts with #!/usr/bin/python and works fine (that is, when I type in ./driver.py at the command prompt the file runs as expected). I have a

Interpreter problem

2005-04-08 Thread Greg Lindstrom
I am using python 2.3.5 on a Linux system and have an odd problem dealing with the 'sha-bang' line. I have a file, driver.py which starts with #!/usr/bin/python and works fine (that is, when I type in ./driver.py at the command prompt the file runs as expected). I have another file, myotherfi