Author belopolsky
Recipients belopolsky, ethan.furman, lemburg, mdcb808@gmail.com, vstinner
Date 2014-12-18.20:43:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418935435.35.0.807157211786.issue23084@psf.upfronthosting.co.za>
In-reply-to
Content
> it would be possible for datetime.datetime.now()
> to avoid the float time.

C implementation of datetime.now() does not rely on float time, so this is only an issue for the Python implementation.

Moreover, as long as datetime keeps its microsecond resolution, float timestamps are good until the next century.

In any case, I don't see how struct_timespec is better than integer expressing time in nanoseconds.

We can implement time.nanotime() returning an int without having to invent a new type.
History
Date User Action Args
2014-12-18 20:43:55belopolskysetrecipients: + belopolsky, lemburg, vstinner, ethan.furman, mdcb808@gmail.com
2014-12-18 20:43:55belopolskysetmessageid: <1418935435.35.0.807157211786.issue23084@psf.upfronthosting.co.za>
2014-12-18 20:43:55belopolskylinkissue23084 messages
2014-12-18 20:43:55belopolskycreate