On Apr 19, 2006, at 12:52, Ronald Oussoren wrote:

       2.1 macpath -- MacOS path manipulation functions


Deprecate. Also note that the 2.4.3 documentation now says "It can  

be used to manipulate old-style Macintosh pathnames on Mac OS X (or  

any other platform)." which is incorrect (it uses POSIX-style  

paths), so delete that sentence.


I'm not a native english speaker, but I read this as "you can use  

this to manipulate OS9 style paths on any platform". Just like you  

can use ntpath to manipulate windows-style paths (c:\foo\bar.txt) on  

any platform. That's actually a useful feature.


As I mentioned in another message this module might be useful to work  

with OS9-style paths as used by some Carbon API's.


Good suggestion, Ronald. I was just tinkering around with appscript and MS Excel a few days ago (still cannot access some things like borders properly and others are just 'bass-ackwards' in the Excel terminology defs so I gave up) but Excel expects colon-separated paths in file paths (yes even in 2004 when they last updated it). SO keeping the OS9 path separator routines is a good idea. I didn't know about them and so wrote my own regex conversion functions (ugh!) as a workaround.
_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig

Reply via email to