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 X-Authentication-Warning: mimosa.csv.warwick.ac.uk: phrxy owned process doing -bs Date: Wed, 3 Oct 2001 14:46:35 +0100 (BST) From: "John J. Lee" X-Sender: To: Subject: RE: spaces in paths in bash, and the FAQ In-Reply-To: <000a01c14c04$676c1040$a300a8c0@nhv> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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). John -- 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/