import statement is case sensitive
ben.hutchings at roundpoint.com
Fri Feb 23 01:46:34 CET 2001
"Alex Martelli" <aleaxit at yahoo.com> writes:
> "Mikael Olofsson" <mikael at isy.liu.se> wrote in message
> news:XFMail.010222145018.mikael at isy.liu.se...
> > On 22-Feb-01 Costas Menico wrote:
> > > Actually I would consider this a shortcoming of Unix. Shipping a
> > > product that depends on the directory names and files being in the
> > > right case must cause all sorts of headaches.
> > Perhaps so, but...
> > I'm still upset over the fact that my Windows box at home doesn't allow
> > me to call a directory "FTP", but changes that to "Ftp" as soon as I
> > hit return. Perhaps there is some setting that I can change, but as a
> > default setting it sucks, IMO.
> I suspect your Windows box DOES allow what you say it doesn't --
> what may currently disallow creation (or display of) all-uppercase
> names is more likely to be the shell GUI front-end (and, yes, it
> IS just a checkbox you can turn off somewhere).
Correct. Windows Explorer (or the underlying folder viewing widget)
does this to any file that doesn't have a "long filename" distinct
from its DOS-compatible file name, but at least some implementations
of the VFAT file-system do not store a separate "long filename" if
the chosen name is already DOS-compatible.
A file named, for example "CAPITALS WITH SPACES" will have that stored
as its "long filename" and something like "CAPITA~1" for DOS
compatibility. Its name will be displayed correctly. A file named
"CAPITALS" will have just that DOS-compatible name stored, and will
be displayed as "Capitals" by default.
Any opinions expressed are my own and not necessarily those of Roundpoint.
More information about the Python-list