This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients r.david.murray, sdaoden, vstinner
Date 2011-05-06.12:17:04
SpamBayes Score 9.3245864e-05
Marked as misclassified No
Message-id <1304684225.13.0.97713664554.issue11999@psf.upfronthosting.co.za>
In-reply-to
Content
Isn't this a bit out of scope for the mailbox module, though?  Mailbox is getting called at irregular intervals, and a clock monitor really wants to be a polling daemon of some sort, I think.  In which case a complete application system that used the mailbox library could adjust the _skewtime appropriately based on the output of a daemon, if it really cares that much.

I think we're well into YAGNI territory, though.  We are only concerned about how long one second is to the filesystem, and a filesystem that skews or jitters more than a tenth of a second over one second is probably pathological anyway.

As for the two second filesystem, my understanding is that is the FAT file system, and I say we just declare using maildir on FAT to be unsupported.  (But I suppose that should be documented).

(As a side note, atime on FAT has a resolution of 1 day, which kind of screws up your "new mail" signal....)
History
Date User Action Args
2011-05-06 12:17:05r.david.murraysetrecipients: + r.david.murray, vstinner, sdaoden
2011-05-06 12:17:05r.david.murraysetmessageid: <1304684225.13.0.97713664554.issue11999@psf.upfronthosting.co.za>
2011-05-06 12:17:04r.david.murraylinkissue11999 messages
2011-05-06 12:17:04r.david.murraycreate