X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: [Ping Python maintainer]: enhancement request Date: Tue, 1 May 2007 14:11:16 +0100 Lines: 29 Message-ID: References: <20070501120623 DOT GA3824 AT tishler DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/2.70.2067 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 * Jason Tishler (Tue, 01 May 2007 08:06:23 -0400) > On Sun, Apr 29, 2007 at 11:58:57PM +0100, Thorsten Kampe wrote: > > I just found out that in the standard Cygwin Python setup it is not > > possible to run the Python interpreter from a Win32 command shell. > > (You get an error about the NTVDM (NT Virtual DOS machine even when C: > > \cygwin\bin is in the path). > > The following works: > > C:\>bash -c python > Python 2.5 (r25:51908, Mar 13 2007, 08:13:14) > ... Yes, of course. It's just the Win32 Shells (Cmd, 4NT) that don't know the Cygwin symlinks > > The reason is that python.exe is a symbolic link to python2.5.exe. As > > the Python interpreter itself is only about 43 Kb in size I suggest > > copying the interpreter instead of symlinking (Zsh for instance does > > the same). > > OK. Should I copy or make a hard link? Both things are actually the same under Cygwin (tested on my FAT32 flash drive and under Windows XP NTFS). NTFS supports hard links but these are likely not the same as the Unix hard links and Cygwin ln does not create the Windows ones. Thorsten -- 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/