Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <80575AFA5F0DD31197CE00805F650D7602D020@wilber.adroit.com> From: "Robinow, David" To: cygwin AT cygwin DOT com Subject: RE: spaces in paths in bash, and the FAQ Date: Wed, 3 Oct 2001 10:56:41 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: John J. Lee [mailto:jjl AT pobox DOT com] > On Wed, 3 Oct 2001, Norman Vine wrote: > > > John J. Lee writes: > [...] > > Just curious -- > > But is there some reason you are not using the Cygwin compiled > > version of Python when working in the Cygwin enviroment ?? > > > > FYI: It reflects the underlying Cygwin POSIX enviroment > > whereas the MSC compiled version doesn't. > > Yes, I'm using a lot of Python extensions which I might have > to recompile > if I used cygwin python -- and a couple are C++, MSVC-only. > I also have > the impression (but maybe I'm wrong) that there is some > overhead involved > in using programs that are linked against the cygwin dll, > which I'm not > keen on (I'm doing numerical stuff). Well, you've screwed yourself by putting spaces in your path. python 2.1 will default to C:\Python21 which is a much more sensible place. I suggest you uninstall python and all your extensions and reinstall them properly. If you're really running interactive you may want to consider running python from the command prompt instead of from bash. ln -s /c/"Program Files"/Python21/python.exe /bin/pywin.exe might work. I haven't tested this extensively. You'll need the "-i" option. Windows python doesn't think you're at a terminal. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/