os.link & NTFS 5

[DP]

I didn't buy the "Python on Win32" book when I had the chance, instead
I bought the regular one. Only because I was being optimistic, and
expected to be working in UNIX. Have been re-considering though...

As for the Win32 APIs, it's the usual conundrup - too little time &
too much to do. I'm not a programmer (or I pretend not to be, lately
I've been feeling otherwise) and would prefer to stick to getting the
task at hand done. On the other hand, limited knowledge of Win32 APIs
has held me back too many times. So it may be a good investment.

Either way, thanks. To everyone. 

I may try the ActiveState mailing lists to see if I can get a better
response. If anyone's interested, please send me an email and I'll
send out a consolidated response (not any time soon though).



yaipa at yahoo.com (yaipa h.) wrote in message news:<6e07b825.0212281208.ee902bf at posting.google.com>...
> Dinil,
> 
> > My experience thus far - links can only be created in Win2k & WinXP,
> > i.e., NTFS 5.
> 
>  Ans. If you want a standard interface use some form of Unix, pick one,
>       else you will always have to deal with shifting uSoft APIs. :(
> 
> > In my judgement, after reading opinions, etc. I think the easiest,
> > though far from elegant, approach is to use an external executable.
> 
>  Ans. Anything you can do in VB you can do in Python.  Don't be afraid
>       of the Win32 APIs provided in the Win32 dist. of Python. In the long
>       run they will serve you well and at some point there will be no 
>       getting around using them. The Win32 API for Python may seem a 
>       little hacky at first, but guess what that is how uSoft does
>       it in VC++ and VB. Again if you don't like the way it feels, UNIX!!
> 
>       The way forward for you is to go out and buy O'Reilly's 'Python 
>       Programming on Win32' and learn it cover to cover. Once you do
>       that, then you will be able to accomplish what you wish.
> 
> Cheers,
> 
> Yaipa.h
>