[Python-Dev] Case sensitive import.

[Steven D. Majewski]

  I don't have Cygwin either and what's more, I don't do much with
MS-Windows, so I'm not familiar with some of the functions called
in that patch.

  HFS+ filesystem on MacOSX is case preserving but case insensitive,
which means that open("File") succeeds for any of: "file","File","FILE" ...
The dirent functions verifies that there is in fact a "File" in that 
directory, and if not continues the search. 

 There was some discussion about whether it should be #ifdef-ed 
diferently or more specifically. I don't know if any other system
than macosx or Cygwin (if it works on that platform) require that
test. (Although I'm glad you got it to compile on Linux, since the
other likely case I can think of is LinuxPPC with a mac filesystem.)
I guess if it compiles, then it doesn't hurt, except for the extra
overhead. ( But, since it continues looking for a match, I couldn't 
use the CHECK_IMPORT_CASE switch. )  

-- Steve 

On Fri, 2 Feb 2001, Barry A. Warsaw wrote:

> First, what is the relationship of patch #103495 with the Cygwin patch
> #103154?  They look like they address similar issues.  Would you say
> that yours subsumes 103154, or at least will solve some of the
> problems jlt63 talks about in his patch?
> 
> The other problem is that I do not have a Cygwin system to test on,
> and my wife isn't (yet :) psyched for me to do much debugging on her
> Mac (which doesn't have MacOSX on it yet).  The best I can do is make
> sure your patch applies cleanly and doesn't break the Linux build.
> Would that work for you for 2.1a2?