Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Tue, 31 Aug 2004 09:58:00 -0400 (EDT)
From:	Andres Corrada-Emmanuel <corrada AT dandenong DOT cs DOT umass DOT edu>
To:	<cygwin AT cygwin DOT com>
Subject:	Re: os.path.join inconsistency?
Message-ID:	<Pine.SOL.4.31.0408310951140.16833-100000@dandenong.cs.umass.edu>
MIME-Version:	1.0

Jason,

I agree the behaviour I'm arguing for is debatable. After taking a look at
ntpath.py and posixpath.py, I see that a satisfactory solution would be
tricky. I'll play around with a made-up hack like cygwinpath.py to see if
it is worth pursuing...

>Andres,

>On Mon, Aug 30, 2004 at 01:29:38PM -0400, Andres Corrada-Emmanuel wrote:
>> Does it not seem inconsistent that if Cygwin Python understands how to
>> execute:
>>
>> file( 'c:/foo/bar' ) as well as file( '/cygdrive/c/foo/bar' )
>>
>> it should also treat Windows style paths correctly with os.path.join?
>> In other words, it seems that Python on Cygwin cannot default to using
>> posixpath.py for os.path. It's got to be posixpath.py with some
>> additional magic to get it to do os.path.join correctly.

>The above is debatable.  You may want to try asking on one of the Python
>lists.


Andres Corrada-Emmanuel
Senior Research Fellow
Information Extraction and Synthesis Laboratory
University of Massachusetts, Amherst



--
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/

- Raw text -