Message361304
I'm not sure which kind of problem you are trying to solve here. time.time() does lose precision because it uses the float type. Comparing time.time() and time.time_ns() tricky because of that. If you care of nanosecond precision, avoid float whenever possible and only store time as integer.
I'm not sure how to compat time.time() float with time.time_ns(). Maybe math.isclose() can help.
I don't think that Python is wrong here, time.time() and time.time_ns() work are expected, and I don't think that time.time() result can be magically more accurate: 1580301619906185300 nanoseconds (int) cannot be stored exactly as floating point number of seconds.
I suggest to only document in time.time() is less accurate than time.time_ns(). |
|
Date |
User |
Action |
Args |
2020-02-03 14:47:56 | vstinner | set | recipients:
+ vstinner, lemburg, rhettinger, mark.dickinson, larry, stutzbach, serhiy.storchaka, vxgmichel |
2020-02-03 14:47:56 | vstinner | set | messageid: <1580741276.57.0.650220493874.issue39484@roundup.psfhosted.org> |
2020-02-03 14:47:56 | vstinner | link | issue39484 messages |
2020-02-03 14:47:56 | vstinner | create | |
|