Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <200406121533.i5CFX0DT015038@mx1.cs.umb.edu>
To: cygwin AT cygwin DOT com
Subject: sys.executable broken under 2.3.4
Reply-to: rouilj AT ieee DOT org
XReturn-Receipt-To: rouilj AT cs DOT umb DOT edu
XDisposition-Notification-To: rouilj AT cs DOT umb DOT edu
Date: Sat, 12 Jun 2004 11:33:00 -0400
From: "John P. Rouillard" <rouilj AT cs DOT umb DOT edu>
X-Scanned-By: MIMEDefang 2.42

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/