At 02:31 PM 6/26/2005 -0500, Skip Montanaro wrote: > Phillip> It has many ways to do the same thing, and many of its property > Phillip> and method names are confusing because they either do the same > Phillip> thing as a standard function, but have a different name (like > Phillip> the 'parent' property that is os.path.dirname in disguise), or > Phillip> they have the same name as a standard function but do something > Phillip> different (like the 'listdir()' method that returns full paths > Phillip> rather than just filenames). > >To the extent that the path module tries to provide a uniform abstraction >that's not saddled with a particular way of doing things (e.g., the Unix way >or the Windows way), I don't think this is necessarily a bad thing.
I'm confused by your statements. First, I didn't notice the path module providing any OS-abstractions that aren't already provided by os.path. Second, using inconsistent and confusing names is pretty much always a bad thing. :) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
