Re: sys.executable broken under 2.3.4

"John P. Rouillard" wrote: > When running python -c "import sys; print sys.executable" it prints > the current working directory rather than the path to python unless > I invoke python with the full path. > > I can't reproduce this on a win 98 box, but on a windows 2k sp4 things > are broken. >

sys.executable broken under 2.3.4

Hi all: I reported this in python 2.2.2 in December, and it's still an issue on one of my systems with python 2.3.4. When running python -c "import sys; print sys.executable" it prints the current working directory rather than the path to python unless I invoke python with the full path. I can't