Win32All On 64-Bit Operating Systems

Tim Daneliuk tundra at
Thu Mar 18 14:43:14 CET 2010

On 3/18/2010 3:54 AM, Tim Golden wrote:
> On 17/03/2010 20:43, Tim Daneliuk wrote:
>> The intent is just to provide as similar as possible a user experience.
>>> From a coding POV, it is surely simpler to just use 'winuser' and
>>> 'wingroup',
>> but I am sort of philosophically wired to not throw information away if
>> it's a available from the OS.
> It's hardly worth disputing I suppose, but I would argue that simply
> presenting the owner & group of a file in Windows is actually doing
> a disservice to the user of the app. It's cluttering up the display
> with information which is essentially useless. Pretty much the only
> time I ever look at a file owner is when I have some knotty security
> issue and I need to assess who might have WRITE_DAC permission. The
> group - never; it really is a relic.
> The file owner & group simply don't play the same role in Windows
> security that they do in *nix. The trouble is that there isn't a
> simple alternative: most files, even with default security, will
> have two or three groups involved in their security at different
> levels.
>> BTW, wanna beta test a really cool CLI mass file renaming tool????? ;)
> Sure -- I'll have a look. But I can't promise any great amount of
> time at present :)

I will announce the Beta for 'tren' here and you (and anyone else) can have at it.

Tim Daneliuk     tundra at
PGP Key:

More information about the Python-list mailing list