This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients Arfrever, Niklas.Claesson, Ramchandra Apte, andrewclegg, belopolsky, goshawk, lemburg, r.david.murray, vstinner
Date 2014-07-14.16:46:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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.
Date User Action Args
2014-07-14 16:46:38belopolskysetrecipients: + belopolsky, lemburg, vstinner, Arfrever, r.david.murray, andrewclegg, Ramchandra Apte, goshawk, Niklas.Claesson
2014-07-14 16:46:38belopolskysetmessageid: <>
2014-07-14 16:46:38belopolskylinkissue15443 messages
2014-07-14 16:46:38belopolskycreate