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 holdenweb
Recipients Arfrever, Niklas.Claesson, Ramchandra Apte, andrewclegg, belopolsky, goshawk, holdenweb, lemburg,, pitrou, pythonhacker, r.david.murray, scoobydoo, serhiy.storchaka, tim.peters, tomikyos, vstinner
Date 2016-07-12.19:52:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Just wanted to add a couple of comments here in case there's any interest. In our missions to make the world's market data available we deal with financial exchanges, many of whom are already recording event data at nanosecond resolution.

Further, I believe the decision to use a separate nanoseconds field to be essentially correct. While  it may well introduce some arithmetical complexity its value in backwards compatibility should be regarded as paramount. If I understand it correctly, the new nanosecond resolution times would continue to be correctly handled (module loss of nanosecond resolution) when handled as current microsecond date-times.
Date User Action Args
2016-07-12 19:52:18holdenwebsetrecipients: + holdenweb, lemburg, tim.peters, belopolsky, pitrou, vstinner, pythonhacker, Arfrever, r.david.murray, andrewclegg, Ramchandra Apte, serhiy.storchaka, goshawk, Niklas.Claesson,, scoobydoo, tomikyos
2016-07-12 19:52:17holdenwebsetmessageid: <>
2016-07-12 19:52:17holdenweblinkissue15443 messages
2016-07-12 19:52:17holdenwebcreate