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, Eli_B, Niklas.Claesson, Ramchandra Apte, andrewclegg, anglister, belopolsky, giampaolo.rodola, goshawk, lemburg, mark.dickinson,, p-ganssle, python-dev, pythonhacker, r.david.murray, scoobydoo, serhiy.storchaka, tim.peters, tomikyos, vstinner
Date 2021-04-07.21:46:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Is there high enough demand for nanoseconds in datetime and time instances?

How often nanosecond timestamps contain anything other than 0s or garbage in the last three digits?

In my experience, all people want to do with such timestamps is to convert them to something expressed in hours, minutes and seconds rather than just a huge number of seconds and back without loosing the value.

A timedelta is almost always a decent replacement for either datetime or time in those cases and sometimes it is even preferable because arithmetically it is closer to numbers.
Date User Action Args
2021-04-07 21:46:00belopolskysetrecipients: + belopolsky, lemburg, tim.peters, mark.dickinson, vstinner, giampaolo.rodola, pythonhacker, Arfrever, r.david.murray, andrewclegg, python-dev, Ramchandra Apte, Eli_B, serhiy.storchaka, goshawk, Niklas.Claesson,, scoobydoo, tomikyos, p-ganssle, anglister
2021-04-07 21:46:00belopolskysetmessageid: <>
2021-04-07 21:46:00belopolskylinkissue15443 messages
2021-04-07 21:46:00belopolskycreate