On 07/29/2011 11:43 PM, Chris Angelico wrote:
> On Sat, Jul 30, 2011 at 6:44 AM, Corey Richardson <kb1...@aim.com> wrote:
>> Excerpts from rantingrick's message of Fri Jul 29 13:22:04 -0400 2011:
>>> * New path module will ONLY support one path sep!
>>
>> People who use windows are used to \ being their pathsep. If you show
>> them a path that looks like C:/whatever/the/path in an app, they are
>> going to think you are nuts. It isn't up to us to decide what anyone
>> uses as a path separator. They use \ natively, so should we. If at
>> any point Windows as an OS starts using /'s, and not support, actually
>> uses (in Windows Explorer as default (or whatever the filebrowser's
>> name is)), it would be great to switch over.
>
> Just tested this: You can type c:/foldername into the box at the top
> of a folder in Explorer, and it works. It will translate it to
> c:\foldername though.
>
> We are not here to talk solely to OSes. We are here primarily to talk
> to users. If you want to display a path to the user, it's best to do
> so in the way they're accustomed to - so on Windows, display
> backslashes.
>
>>> - normcase --> path = path.lower()
>>
>> Not quite, here are a few implementations of normcase (pulled from 2.7)
>>
>> # NT
>> return s.replace("/", "\\").lower()
>>
>> # Mac (Correct in this case)
>> return path.lower()
>>
>> # POSIX
>> return s
>>
>> But I can't think of where I would ever use that. Isn't case important on
>> Windows?
>
well normcase might help to find out, whether two filenames are the same.
under unix 'myfile' and 'myFile' would be different
under windows they would refer to the same file.
normcase (perhaps to be combined with normpath) can tel you this.
--
http://mail.python.org/mailman/listinfo/python-list
