X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.8 required=5.0 tests=BAYES_50
X-Spam-Check-By:	sourceware.org
X-Authenticated-User:	jim.eberle.fastnlight.com
Message-ID:	<5E0CC230268C4E638A8C3318492EB340@thinkpad>
From:	"Jim Eberle" <jim DOT eberle AT fastnlight DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	File extension for the copy of python2.5.exe
Date:	Sat, 1 May 2010 09:37:22 -0700
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

Part of the latest python rollout involved converting the "python" symlink 
into a full file copy. I was wondering if this could be renamed to 
"python.exe".

Without the ".exe" extension, doing a CreateProcess() on "python" fails even 
if the python file exists and is in the calling process' %PATH%.

Likewise, running "python" from a CMD shell (some people do this) fails for 
the same reason.

I don't think this would break things on the Cygwin side -- witness 
"ls.exe".

Thanks,
Jim



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

- Raw text -