|Marked as misclassified
So two things here:
1. Jython 2.7 implements the change seen in the Python 2.7 language that the repr of a float uses the shortest decimal fraction that represents the same underlying binary representation. That's why you are seeing in 2.5 formatted values like '2015-10-23T22:24:56.303999' (truncated) vs what would now the more accurate (given truncation) '2015-10-23T22:24:56.304000'
2. I tried java.lang.time.Instant.now() to get instants and corresponding epoch seconds and nanoseconds. On OS X 10.11 and Ubuntu 15.04, using latest Oracle Java 8 for each, the nanoseconds reported are still with millesecond precision:
>>> import java
>>> t = java.time.Instant.now()
There may be a configuration of Java and underlying OS and hardware that allows us to get wall clock time with greater precision (and presumably accuracy - I think Java here is preventing false accuracy, which is a good thing), but I don't have that setup.
Please retry this experiment on your own setup. I will also look at Java 9 as part of some other work, but I don't expect any difference.
|2015-10-23 15:52:16||zyasoft||set||messageid: <firstname.lastname@example.org>|
+ zyasoft, DanglingPointer|
|2015-10-23 15:52:16||zyasoft||link||issue2411 messages|