Alexander Belopolsky added the comment:
Given that struct timespec defined as
struct timespec {
time_t tv_sec; /* seconds */
long tv_nsec; /* nanoseconds */
};
is slowly becoming the prevailing standard to represent time in system
interfaces, Python's inability to faithfully store it in a high level object
will increasingly become a handicap.
People are starting to put nanoseconds in their databases not because they
really need such precision, but because this is what they get from their
devices and at the collection time cannot do anything "smart".
The program that collects the events may simply not have time to do anything
other than store raw data, or not have the higher level knowledge of what is
the proper rounding.
The proper rounding is best to be done at the analysis time and by a program
written in a higher level language such as Python.
----------
assignee: -> belopolsky
stage: -> needs patch
versions: +Python 3.5 -Python 3.4
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue15443>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
