homepage

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 neologix
Recipients db3l, nadeem.vawda, ncoghlan, neologix, skrah
Date 2012年02月27日.21:50:03
SpamBayes Score 0.0009715219
Marked as misclassified No
Message-id <1330379403.87.0.0831142213856.issue14131@psf.upfronthosting.co.za>
In-reply-to
Content
Does Windows still have its once per day/week/whatever time synchronization, or does it use a proper NTP client?
Because this offset is way too large for a broken RTC lock, so it might simply be some process adjusting the clock behind our back (although it's too much for a typical NTP client, at least on Unix).
It could be interesting to replace time.time() by the new time.monotonic().
History
Date User Action Args
2012年02月27日 21:50:04neologixsetrecipients: + neologix, db3l, ncoghlan, nadeem.vawda, skrah
2012年02月27日 21:50:03neologixsetmessageid: <1330379403.87.0.0831142213856.issue14131@psf.upfronthosting.co.za>
2012年02月27日 21:50:03neologixlinkissue14131 messages
2012年02月27日 21:50:03neologixcreate

AltStyle によって変換されたページ (->オリジナル) /