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" To: Subject: File extension for the copy of python2.5.exe Date: Sat, 1 May 2010 09:37:22 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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