From: "deckerben" <bdeck AT lycos DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
References: <3ef8c2c7$0$150$9b622d9e AT news DOT freenet DOT de> <2593-Wed25Jun2003075056+0300-eliz AT elta DOT co DOT il>
Subject: Re: dirent->d_name returns lowercase?
Date: Wed, 25 Jun 2003 20:42:56 +0200
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Lines: 26
Message-ID: <3ef9ebcd$0$149$9b622d9e@news.freenet.de>
NNTP-Posting-Host: 213.7.8.232
X-Trace: 1056566221 news.freenet.de 149 213.7.8.232:1695
X-Complaints-To: abuse AT freenet DOT de
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


"Eli Zaretskii" <eliz AT elta DOT co DOT il> wrote in message
news:2593-Wed25Jun2003075056+0300-eliz AT elta DOT co DOT il...
> > From: "deckerben" <bdeck AT lycos DOT co DOT uk>
> > Newsgroups: comp.os.msdos.djgpp
> > Date: Tue, 24 Jun 2003 23:34:01 +0200
> This is not the default because in most situations the behavior you
> see now is what users want, especially if they have files that come
> from DOS (where _all_ directory entries are in UPPERCASE).

I really understand the DOS issue. But this would not be true under NT
systems, where true filename cases are reported correctly. Fooling with this
causes problems. I was wondering why during some Python distutil builds, it
was *supposed* to create an upper-case subdirectory, only to create a
lower-case one, etc. I was banging my head wondering why the glob test was
failing (I thought something was *really* wrong).

One option is that users set "PYTHONCASEOK". But this only resolves module
import case sensitivity.

I am recommending all NT-based PythonD users to set FNCASE=y.

regards,
Ben