[MERGE] Stop treating Permission Denied as lock contention
John Arbash Meinel
john at arbash-meinel.com
Wed Jan 31 19:36:40 GMT 2007
Aaron Bentley wrote:
> Alexander Belchenko wrote:
>> John Arbash Meinel ?8H5B:
>> test_lockdir.TestLockDir.test_lock_permission FAIL
>> 608ms
>> PermissionDenied not raised
>
> Damn. Thanks for testing. I'll see what the win32 behavior should be,
> and update my test.
>
> Aaron
I'm guessing the problem is that os.chmod(444) isn't actually making the
file readonly. I'm not sure if Alexander is testing on FAT32 or NTFS,
but I seem to recall having problems setting a readonly flag on windows
files.
I know I've definitely had problems for directories. Because there
doesn't seem to be a separate permission for the directory versus the
files inside the directory. (I can open up the dialog box and set
readonly on the dir, and it asks if I want to apply it to all child
files, but when I open it up again it comes back with the square rather
than a check, which generally means => some are readonly, some aren't).
And after doing so, I was still able to create files inside that
directory. So obviously it wasn't readonly.
I wish I knew more to tell you.
But as near as I can tell, you can't make a directory readonly on Win32.
Sorry I didn't remember this earlier.
John
=:->
More information about the bazaar
mailing list