Steffen Daode Nurpmeso <sdao...@googlemail.com> added the comment: On Fri, 6 May 2011 04:44:00 +0200, R. David Murray wrote: > [.] the mtime only has a resolution of one second.
You always say that! But i'm pretty sure from somewhen long ago that there are filesystems which have a two second time resolution. And unless i'm mistaken that filesystem is still used widely. > Attached is a patch implementing the fix. > It undoes the 6896 patch I've not yet tried your code but from looking at the patch it seems to target towards a real approach. > I also added an additional delta in case the file system clock > is skewing relative to the system clock. I made this a class > attribute so that it is adjustable; perhaps it should be made > public and documented. On the other hand, if it shows up after almost five years that the one second resolution solution doesn't work, and that simply adjusting to a two second resolution is not smart enough to get this fixed, then i would not go for something half-automatic which a user needs to adjust manually, because how could a user do that? Thus, in my view, if you are *really* looking forward to make mailbox.py a *good* and *beautiful* thing then the timedelta in between the filesystem and the host's time() must of course be tracked-, and the fuzziness should be adjusted automatically. E.g. similar http://linuxcommand.org/man_pages/adjtimex8.html. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11999> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
