sys.executable broken under 2.3.4

["John P. Rouillard" <rouilj at cs dot umb dot edu>]

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 reproduce this on a win 98 box, but on a windows 2k sp4 things
are broken.

Can anybody reproduce this?

Also does anybody have any ideas on how to find out what is happening
without having to rebuild python and run a debugger through it?

Am I correct in assuming that the problem is in the python binary and
not is some python library?

				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/