Problem with sys.executable solved

2004-06-13 Thread John P. Rouillard
I wrote a bit ago about sys.executable returning the current working directory. I am happy to report that the problem is solved, but I am not sure what caused the problem in the first place. The permissions on python2.3 were mode 000. This allowed python to run, but didn't allow it to do other

RE: Problem with sys.executable solved

2004-06-13 Thread John Morrison
From: John P. Rouillard The permissions on python2.3 were mode 000. This allowed python to run, but didn't allow it to do other things like resolve its own name. chmod 755 /usr/bin/python2.3.exe fixed the sys.executable problem. $ python -V Python 2.3.4 $ ls -liash /usr/bin/python2.3.exe

Re: Problem with sys.executable solved

2004-06-13 Thread Larry Hall
At 12:36 PM 6/13/2004, you wrote: I wrote a bit ago about sys.executable returning the current working directory. I am happy to report that the problem is solved, but I am not sure what caused the problem in the first place. The permissions on python2.3 were mode 000. This allowed python to run,