Tim Peters wrote: > and filecmp contains a module-level _cache with a funky scheme for > avoiding file comparisons if various os.stat() values haven't changed. > But st_mtime on Windows doesn't necessarily change when a file is > modified -- it has limited resolution (2 seconds on FAT32, and I'm > having a hard time finding a believable answer for NTFS (which I'm > using)).
The time stamp itself has a precision of 100ns (it really is a FILETIME). I don't know whether there is any documentation that explains how often it is updated; I doubt it has a higher resolution than the system clock :-) > Anyone bored enough to report what happens on Linux? I had to run it 18 times to get test_exceptions beginning 42 repetitions 123456789012345678901234567890123456789012 .......................................... test_exceptions leaked [203, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] references 1 test OK. Regards, Martin _______________________________________________ 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
