Message304365
| Author | vstinner |
|---|---|
| Recipients | vstinner |
| Date | 2017-10-13.21:34:15 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1507930455.75.0.213398074469.issue31784@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
time.time() returns time as a float, but the conversion to float lose precision at the nanosecond resolution. I propose to add a new time.time_ns() function which returns time as an integer number of nanoseconds since epoch. It's similar to the st_mtime_ns field of os.stat_result which extended the old st_mtime field. For the full rationale, see my thread on python-ideas: [Python-ideas] Add time.time_ns(): system clock with nanosecond resolution https://mail.python.org/pipermail/python-ideas/2017-October/047318.html |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2017-10-13 21:34:15 | vstinner | set | recipients: + vstinner |
| 2017-10-13 21:34:15 | vstinner | set | messageid: <1507930455.75.0.213398074469.issue31784@psf.upfronthosting.co.za> |
| 2017-10-13 21:34:15 | vstinner | link | issue31784 messages |
| 2017-10-13 21:34:15 | vstinner | create | |