Mail Archives: djgpp/2003/06/30/09:45:23
"Eli Zaretskii" <eliz AT elta DOT co DOT il> wrote in message news:<3405-Sun29Jun2003205545+0300-eliz AT elta DOT co DOT il>...
> > From: "deckerben" <bdeck AT lycos DOT co DOT uk>
> > Newsgroups: comp.os.msdos.djgpp
> > Date: Sun, 29 Jun 2003 12:28:09 +0200
> > > >
> > > > D:\>set FNCASE=n
> > > > D:\>ls -al
> > > > total 1617
> > > > drwxr-xr-x 17 bdeck root 608 Jun 17 01:13 .
> > > > drwxr-xr-x 17 bdeck root 608 Jun 17 01:13 ..
> > > > -rw-r--r-- 1 bdeck root 708836 Jun 16 01:10 Citizenship docs1.zip
> > >
> > > This isn't NT, it probably is Windows 2000 or XP. Windows NT doesn't
> > > support long file names at all, so the only way you could see the
> > > above is if you have NTLFN installed on that system.
> >
> > PythonD doesn't run on a configuration that doesn't support long filenames
> > anyhow. It's special :-)
>
> The above output was from `ls', not from PythonD.
And that matters? Everyone that wants PythonD needs long filename
support. Once that support is installed, it affects all DJGPP
programs, not just PythonD. That's why I can't understand the big
tragedy of using FNCASE=y under NT... the configuration is *anyway*
changed. FNCASE=y would just take better advantage of it (NTLFN seems
to always be right with filecases, which is the issue here anyway).
If you want to stick with old 8.3 conventions under NT, don't install
PythonD (although I can't dream of why).
I am considering changing the base library directory name, the entries
in site.py, posixpath.py, and lib-dynaload so that some *basic*
library support is available without LFN.
I am not considering rewriting the whole python library. I do not
intend to break general python compatibilty in any way. Any files that
*might* get changed will be copied (except the directory names and
site.py itself). Anyone wishing to use distutils, unicode, or 3rd
party libraries in any way will need LFN support.
Ben
- Raw text -