Alexander Belopolsky added the comment: > 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23084> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
